[SPARK-54021][Geo][SQL] Implement Geography and Geometry accessors across Catalyst #52723
+208
−8
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
dongjoon-hyun
changed the title
|
@mkaravel @szehon-ho @cloud-fan Please review. |
uros-db
changed the title
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?
Added Geography and Geometry accessors to core row/column interfaces, extended codegen and physical type handling to properly recognize geospatial types, enabled writing/reading of Geography and Geometry values in unsafe writer, and added other necessary plumbing for Geography and Geometry in projection/row utilities in order to thread through the new accessors.
Note that the GEOMETRY and GEOGRAPHY physical types were recently included to Spark SQL as part of: #52629.
Why are the changes needed?
To provide first-class support for GEOGRAPHY and GEOMETRY within Catalyst.
Does this PR introduce any user-facing change?
No.
How was this patch tested?
Added new tests to:
GenerateUnsafeProjectionSuite.scalaUnsafeRowWriterSuite.scalaWas this patch authored or co-authored using generative AI tooling?
No.