fix(parquet/pqarrow): normalize the element name in the stored ARROW:schema#746
Open
zeroshade wants to merge 4 commits intoapache:mainfrom
Open
fix(parquet/pqarrow): normalize the element name in the stored ARROW:schema#746zeroshade wants to merge 4 commits intoapache:mainfrom
zeroshade wants to merge 4 commits intoapache:mainfrom
Conversation
The lint fix in the previous commit incorrectly transformed the condition:
!(A && !B && C) -> (nil || !B && !IsNone || !C)
The correct transformation is:
nil || B || !C
Also restores use of n.decimalMetaData instead of DecimalMetadata{} in the
IsCompatible call, which was also changed incorrectly.
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Rationale for this change
closes #744
What changes are included in this PR?
Normalizes the element name of list fields in the stored ARROW:schema of a parquet file to avoid mismatches.
Are these changes tested?
Yes, a new unit test is added.
Are there any user-facing changes?
Yes, should be a bug fix to ensure consistency.