[SPARK-53922][Geo][SQL] Introduce physical Geometry and Geography types #52629
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
uros-db
commented
Oct 16, 2025
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.
What changes were proposed in this pull request?
Introduce two new physical types to Spark:
PhysicalGeographyTypePhysicalGeometryTypeThis PR also adds appropriate mapping from the logical geospatial types (introduced in: #52491) to the new physical types.
Why are the changes needed?
Extending the implementation of GEOMETRY and GEOGRAPHY types in Spark, laying the groundwork for full geospatial data type support.
Does this PR introduce any user-facing change?
No.
How was this patch tested?
Added new tests to:
GeographyValSuiteGeometryValSuiteAlso, added appropriate test cases to:
GeographyTypeSuiteGeographyTypeSuiteWas this patch authored or co-authored using generative AI tooling?
No.