-
Notifications
You must be signed in to change notification settings - Fork 29k
[SPARK-54166][Geo][PYTHON] Introduce type encoders for geospatial types in PySpark #52861
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
@uros-db the test failures seems related |
|
@zhengruifeng @HyukjinKwon @cloud-fan All checks good now. |
uros-db
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
#52930 is merged, so this PR is ready to move on.
dongjoon-hyun
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+1, LGTM. Thank you, @uros-db and all.
Merged to master/4.1.
…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 <[email protected]> Signed-off-by: Dongjoon Hyun <[email protected]> (cherry picked from commit d304a03) Signed-off-by: Dongjoon Hyun <[email protected]>
…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. Closes apache#52861 from uros-db/geo-pyspark-encoders. Authored-by: Uros Bojanic <[email protected]> Signed-off-by: Dongjoon Hyun <[email protected]>
…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. Closes apache#52861 from uros-db/geo-pyspark-encoders. Authored-by: Uros Bojanic <[email protected]> Signed-off-by: Dongjoon Hyun <[email protected]>
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.