Uh oh!
There was an error while loading. Please reload this page.
[SPARK-54166][Geo][PYTHON] Introduce type encoders for geospatial types in PySpark - #52861
Closed
uros-db wants to merge 14 commits into
Closed
[SPARK-54166][Geo][PYTHON] Introduce type encoders for geospatial types in PySpark#52861uros-db wants to merge 14 commits into
uros-db wants to merge 14 commits into
Conversation
This comment was marked as outdated.
This comment was marked as outdated.
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
This comment was marked as outdated.
This comment was marked as outdated.
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
uros-db
marked this pull request as draft
November 4, 2025 07:42
uros-db
marked this pull request as ready for review
November 5, 2025 19:45
This comment was marked as outdated.
This comment was marked as outdated.
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
HyukjinKwon
approved these changes
Nov 5, 2025
zhengruifeng
commented
Nov 7, 2025
Contributor
@uros-db the test failures seems related |
uros-db
marked this pull request as draft
November 7, 2025 06:00
uros-db
marked this pull request as ready for review
November 8, 2025 04:58
uros-db
commented
Nov 8, 2025
ContributorAuthor
@zhengruifeng@HyukjinKwon@cloud-fan All checks good now. |
dongjoon-hyun
approved these changes
Nov 8, 2025
dongjoon-hyun
left a comment
Member
There was a problem hiding this comment.
+1, LGTM. Thank you, @uros-db and all.
Merged to master/4.1.
dongjoon-hyun pushed a commit
that referenced
this pull request
Nov 8, 2025
…es in PySpark ### What changes were proposed in this pull request? This PR introduces type encoders for `Geography` and `Geometry` in PySpark. Note that Scala-side encoders for geospatial types were added in: #52813. ### Why are the changes needed? Expanding client support for geospatial types in PySpark API. ### Does this PR introduce _any_ user-facing change? No. ### How was this patch tested? New PySpark unit tests: - `test_types` - `test_parity_types` ### Was this patch authored or co-authored using generative AI tooling? No. Closes#52861 from uros-db/geo-pyspark-encoders. Authored-by: Uros Bojanic <uros.bojanic@databricks.com> Signed-off-by: Dongjoon Hyun <dongjoon@apache.org> (cherry picked from commit d304a03) Signed-off-by: Dongjoon Hyun <dongjoon@apache.org>
zifeif2 pushed a commit
to zifeif2/spark
that referenced
this pull request
Nov 22, 2025
…es in PySpark ### What changes were proposed in this pull request? This PR introduces type encoders for `Geography` and `Geometry` in PySpark. Note that Scala-side encoders for geospatial types were added in: apache#52813. ### Why are the changes needed? Expanding client support for geospatial types in PySpark API. ### Does this PR introduce _any_ user-facing change? No. ### How was this patch tested? New PySpark unit tests: - `test_types` - `test_parity_types` ### Was this patch authored or co-authored using generative AI tooling? No. Closesapache#52861 from uros-db/geo-pyspark-encoders. Authored-by: Uros Bojanic <uros.bojanic@databricks.com> Signed-off-by: Dongjoon Hyun <dongjoon@apache.org>
huangxiaopingRD pushed a commit
to huangxiaopingRD/spark
that referenced
this pull request
Nov 25, 2025
…es in PySpark ### What changes were proposed in this pull request? This PR introduces type encoders for `Geography` and `Geometry` in PySpark. Note that Scala-side encoders for geospatial types were added in: apache#52813. ### Why are the changes needed? Expanding client support for geospatial types in PySpark API. ### Does this PR introduce _any_ user-facing change? No. ### How was this patch tested? New PySpark unit tests: - `test_types` - `test_parity_types` ### Was this patch authored or co-authored using generative AI tooling? No. Closesapache#52861 from uros-db/geo-pyspark-encoders. Authored-by: Uros Bojanic <uros.bojanic@databricks.com> Signed-off-by: Dongjoon Hyun <dongjoon@apache.org>
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 freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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?
This PR introduces type encoders for
GeographyandGeometryin PySpark.Note that Scala-side encoders for geospatial types were added in: #52813.
Why are the changes needed?
Expanding client support for geospatial types in PySpark API.
Does this PR introduce any user-facing change?
No.
How was this patch tested?
New PySpark unit tests:
test_typestest_parity_typesWas this patch authored or co-authored using generative AI tooling?
No.