formalize the default map field names to match default arrow spec - #10517
Merged
Conversation
…t arrow spec (apache#10297)" (apache#10506) This reverts commit ed92960.
github-actions
Bot
added
parquet
alamb
added
api-change
14 tasks
rluvaton
approved these changes
Aug 2, 2026
etseidl
approved these changes
Aug 3, 2026
Jefffrey
changed the title
Jefffrey
approved these changes
Aug 4, 2026
Contributor
|
thanks all |
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
4 participants
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.
This reverts commit ed92960.
Which issue does this PR close?
Rationale for this change
As part of the 59.2.0 release, I found that the changes in #10297 from @rluvaton required downstream modifications and thus were not appropriate for a point release.
Thus I reverted the changes in #10506 until the next breaking release (60.0.0)
What changes are included in this PR?
Are these changes tested?
Yes
Are there any user-facing changes?
Yes, the names of fields in MapArrays are now consistent ("key" and "value" always, rather than sometimes "keys" and "values")