refactor(schema): use REE field name constants - #11064
Open
akashchamp wants to merge 1 commit into
Open
Conversation
Replace default run-end encoded field-name literals with the shared constants.
Rich-T-kid
approved these changes
Sep 12, 2026
Rich-T-kid
left a comment
Contributor
There was a problem hiding this comment.
seems straightforward, thank you @akashchamp
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
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.
Closes #11035
Assisted-by: Codex
Summary
Use the existing REE default field-name constants wherever
arrow-schemaconstructs fields with the defaultrun_endsandvaluesnames. Intentional customnamed_valuesparsing and display cases remain unchanged.Testing
cargo fmt --all -- --checkcargo test -p arrow-schema— 108 unit tests and 41 doctests passed.cargo test -p arrow-schema --all-features— 179 unit tests and 43 doctests passed.cargo clippy -p arrow-schema --all-targets --all-features -- -D warningsnamed_valuesschema; each parsed back to the original data type.User-facing changes
None.
AI assistance was used to identify and apply the mechanical substitutions. I reviewed every changed construction and confirmed custom-name cases remain explicit.