[SPARK-56771][SQL] Enable geospatial support by default#55734
Open
uros-db wants to merge 1 commit intoapache:masterfrom
Open
[SPARK-56771][SQL] Enable geospatial support by default#55734uros-db wants to merge 1 commit intoapache:masterfrom
uros-db wants to merge 1 commit intoapache:masterfrom
Conversation
uros-db
commented
May 7, 2026
Contributor
Author
uros-db
left a comment
There was a problem hiding this comment.
@cloud-fan Please review.
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
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.
What changes were proposed in this pull request?
With geospatial types implemented in Spark (https://issues.apache.org/jira/browse/SPARK-51658), we can now enable the corresponding SQL config by default.
Why are the changes needed?
Enable geospatial support by default in Spark 4.2.
Does this PR introduce any user-facing change?
Yes, geospatial types and expressions are now enabled by default.
How was this patch tested?
Existing tests suffice, this is a config-only change.
Was this patch authored or co-authored using generative AI tooling?
No.