PARQUET-2456: Avoid type name conflicts on fixed type #1304
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
Fixed types with identical names create name type conflicts
wgtmac
approved these changes
Apr 2, 2024
RustedBones
changed the title
|
Sure! Here it is: https://issues.apache.org/jira/browse/PARQUET-2456 |
RustedBones
changed the title
wgtmac
changed the title
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.
Fixed types with identical names create name type conflicts
For instance, if a parquet message type contains several repeated fixed types, the following error will be thrown:
Use the same conflict resolution trick used for record types.