fix issue with segment metadata cache and complex types when doing out of order upgrades from 0.22 #14948
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Fixes an issue with complex type handling that was intended to be fixed as part of #12016 to handle cases where the broker is updated before historical and realtime nodes.
Since complex types were sending back the response with just the complex type name, the valueType was still null resulting in errors of the form:
I will update the release notes of 0.23 to indicate that the brokers must be updated last for now...
This PR has: