[SEDONA-457] Don't write GeometryUDT into org.apache.spark.sql.parquet.row.metadata when writing GeoParquet files #1164
Conversation
This file contains 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
…a. This is for maximum compatibility with various versions of Apache Sedona.
jiayuasu
approved these changes
Dec 29, 2023
|
This PR will fix OvertureMaps/data#89 |
Kontinuation
added a commit
to Kontinuation/sedona
that referenced
this pull request
Oct 11, 2024
…t.row.metadata when writing GeoParquet files (apache#1164) * Don't write GeometryUDT into org.apache.spark.sql.parquet.row.metadata. This is for maximum compatibility with various versions of Apache Sedona. * Apply this patch to Spark 3.4 and Spark 3.5
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.
Did you read the Contributor Guide?
Is this PR related to a JIRA ticket?
[SEDONA-XXX] my subject.What changes were proposed in this PR?
Spark SQL primarily uses
org.apache.spark.sql.parquet.row.metadatato infer the schema of parquet files. It will fall back to using the native parquet schema only whenorg.apache.spark.sql.parquet.row.metadatais absent. Writing the schema of dataframes with GeometryUDT columns intoorg.apache.spark.sql.parquet.row.metadatamay cause compatibility problems. Please refer to the JIRA ticket for more details.This patch replaces the GeometryUDT written into the metadata with binary type, since this is the physical data type for representing geometry values.
How was this patch tested?
Add assertions to verify that the metadata written by Spark SQL does not contain GeometryUDT.
Did this PR include necessary documentation updates?