[SPARK-56813][DOCS] Refine the documentation for geospatial types and functions#55790
Open
uros-db wants to merge 1 commit into
Open
[SPARK-56813][DOCS] Refine the documentation for geospatial types and functions#55790uros-db wants to merge 1 commit into
uros-db wants to merge 1 commit into
Conversation
uros-db
commented
May 10, 2026
Contributor
Author
uros-db
left a comment
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
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?
Tighten the geospatial documentation:
sql-ref-geospatial-types.md: update the documentation for supported ST functions.sql-ref-datatypes.md: drop unparameterized type syntax from the SQL and PySpark.sql-ref-functions-builtin.md: surfacest_funcsgroup as Geospatial ST Functions.sql-migration-guide.md: note that geospatial types and ST functions are enabled since 4.2.Why are the changes needed?
Fix gaps and accuracy for geospatial documentation.
Does this PR introduce any user-facing change?
No.
How was this patch tested?
Existing tests suffice for docs only changes.
Was this patch authored or co-authored using generative AI tooling?
Generated-by: Claude Opus 4.7.