[SPARK-52029][SQL] Support external field-id to column-name mapping for Parquet #50819
+1,161
−53
Conversation
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
…port Co-authored-by: Hao Jiang <harperjiang@msn.com>
# for free
to join this conversation on GitHub.
Already have an account?
# 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.
Co-authored with @harperjiang
What changes were proposed in this pull request?
Add spark.sql.parquet.fieldId.read.externalMapping to allow specifying external field id to name mapping for Parquet file format.
Why are the changes needed?
Similar to Iceberg's schema.name-mapping.default (https://iceberg.apache.org/spec/#column-projection)
Add support for Spark parquet file format to also be able to specify an external mapping, so we can read externally-created files added to the table, with field-ids not in the existing table schema.
Does this PR introduce any user-facing change?
No
How was this patch tested?
Added new test in ParquetIdExternalMappingSuite
Was this patch authored or co-authored using generative AI tooling?
No