Disable write/read Parquet when Parquet field IDs are used #4882
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.
Temporarily disable write/read parquet when schema has a specified Parquet field ID
Solution is: Fallback to CPU when writing Parquet with field id column. Fallback to CPU if
"spark.sql.parquet.fieldId.read.enabled" is true when reading Parquet.
Contributes #4846
Signed-off-by: Chong Gao res_life@163.com