[LI] Make MergeHiveSchemaWithAvro not reordering avro optional union … #153
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…field when it's it's merging a hive primitive with an avro optional union
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
…field when it's it's merging a hive primitive with an avro optional union
This patch fixes a issue when a table's avro schema exhibit this pattern: it has a record field which has a inner optional field with null as the second element, and it has a default value at the record level with a key-value pair for that inner optional field, then the current
MergeHiveSchemaWithAvrowill reorder the null to be the first element of the optional field schema, making the record-level default validation fail. This patch will retain the positional of thenullelement in the avro optional field its original position, thus fixing the bug.