test: enumerate PyArrow primitive type mappings - #3919
Open
emecii wants to merge 1 commit into
Open
Conversation
Generated-by: OpenAI Codex (GPT-6)
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.
Closes #3714
Rationale for this change
PyArrow-to-Iceberg conversion tests cover supported primitive types individually, but the expected PyArrow and Iceberg-spec Parquet physical mappings are not collected in one contract. This table-driven test covers the supported primitive mappings, including UUID, fixed binary, timestamp variants, and all three decimal physical-width bands.
Are these changes tested?
make test PYTEST_ARGS='-q'— 4,033 passed, 3 skipped, 1,571 integration-marked tests deselected by the project target.make check-licensecould not run locally because no Java runtime is installed. This PR changes one existing test file and adds no source files.Are there any user-facing changes?
No runtime behavior changes. The expanded regression contract protects type-conversion compatibility.