Uh oh!
There was an error while loading. Please reload this page.
[SPARK-54253][Geo][SQL] Add a guarding config for geospatial support - #53009
[SPARK-54253][Geo][SQL] Add a guarding config for geospatial support#53009uros-db wants to merge 22 commits into
Conversation
dongjoon-hyun
left a comment
There was a problem hiding this comment.
Nice! Thank you so much for proposing this new configuration, @uros-db .
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
uros-db
left a comment
There was a problem hiding this comment.
I'm converting this PR to draft while I figure out how to enforce the config in testing for Connect (e.g. ArrowEncoderSuite) and clear those failures. Not sure how to do this at the moment, because static SQL config values can't be changed, and modifying testConfigs in SparkConnectServerUtils doesn't help either because isTesting stays false and config value is not propagated between server & client.
dongjoon-hyun
commented
Nov 13, 2025
Gentle ping, @uros-db . If there is no way, please turn it |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
dongjoon-hyun
commented
Nov 17, 2025
Please let me know when you are ready, @uros-db . |
| */ | ||
| def geospatialTypeWithSrid(sourceType: DataType, srid: Expression): DataType = { | ||
| sourceType match { | ||
| case _ if !SQLConf.get.geospatialEnabled => |
There was a problem hiding this comment.
is it a narrow waist for geo functionalities?
There was a problem hiding this comment.
Yes, this is very narrow wrt. geo. It's exclusively used in ST expressions (currently only 1 expression, but will be re-used in a few more) to determine the resulting dataType.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
uros-db
commented
Nov 19, 2025
Hi folks all checks are good here, and I marked the PR ready as for review. @cloud-fan@dongjoon-hyun@holdenk |
cloud-fan
commented
Nov 19, 2025
thanks, merging to master/4.1! |
### What changes were proposed in this pull request? Introduce a new SQL config for controlling the geospatial feature: ``` spark.sql.geospatial.enabled ``` The default value is `false`, and enabled only in testing. ### Why are the changes needed? Guard the geospatial feature until it's fully finished. ### Does this PR introduce _any_ user-facing change? No. ### How was this patch tested? Added appropriate unit tests to confirm that the config is effective: - `STExpressionsSuite` ### Was this patch authored or co-authored using generative AI tooling? No. Closes#53009 from uros-db/geo-config. Authored-by: Uros Bojanic <uros.bojanic@databricks.com> Signed-off-by: Wenchen Fan <wenchen@databricks.com> (cherry picked from commit d299684) Signed-off-by: Wenchen Fan <wenchen@databricks.com>
dongjoon-hyun
commented
Nov 19, 2025
Thank you so much, @uros-db , @cloud-fan and all. |
### What changes were proposed in this pull request? Introduce a new SQL config for controlling the geospatial feature: ``` spark.sql.geospatial.enabled ``` The default value is `false`, and enabled only in testing. ### Why are the changes needed? Guard the geospatial feature until it's fully finished. ### Does this PR introduce _any_ user-facing change? No. ### How was this patch tested? Added appropriate unit tests to confirm that the config is effective: - `STExpressionsSuite` ### Was this patch authored or co-authored using generative AI tooling? No. Closesapache#53009 from uros-db/geo-config. Authored-by: Uros Bojanic <uros.bojanic@databricks.com> Signed-off-by: Wenchen Fan <wenchen@databricks.com>
…ig in Spark Connect ### What changes were proposed in this pull request? A new SQL config (`spark.sql.geospatial.enabled`) was introduced as part of #53009. However, the original PR didn't fully gate geospatial functionality, so this PR also forbids geo dataframes in Spark Connect. ### Why are the changes needed? Guard the geospatial feature until it's fully finished. ### Does this PR introduce _any_ user-facing change? No. ### How was this patch tested? Added appropriate unit tests to confirm that the config is effective: - `GeographyConnectDataFrameSuite` - `GeometryConnectDataFrameSuite` ### Was this patch authored or co-authored using generative AI tooling? No. Closes#53259 from uros-db/geo-config_connect_tests. Authored-by: Uros Bojanic <uros.bojanic@databricks.com> Signed-off-by: Wenchen Fan <wenchen@databricks.com>
…ig in Spark Connect ### What changes were proposed in this pull request? A new SQL config (`spark.sql.geospatial.enabled`) was introduced as part of #53009. However, the original PR didn't fully gate geospatial functionality, so this PR also forbids geo dataframes in Spark Connect. ### Why are the changes needed? Guard the geospatial feature until it's fully finished. ### Does this PR introduce _any_ user-facing change? No. ### How was this patch tested? Added appropriate unit tests to confirm that the config is effective: - `GeographyConnectDataFrameSuite` - `GeometryConnectDataFrameSuite` ### Was this patch authored or co-authored using generative AI tooling? No. Closes#53259 from uros-db/geo-config_connect_tests. Authored-by: Uros Bojanic <uros.bojanic@databricks.com> Signed-off-by: Wenchen Fan <wenchen@databricks.com> (cherry picked from commit 38d6010) Signed-off-by: Wenchen Fan <wenchen@databricks.com>
What changes were proposed in this pull request?
Introduce a new SQL config for controlling the geospatial feature:
The default value is
false, and enabled only in testing.Why are the changes needed?
Guard the geospatial feature until it's fully finished.
Does this PR introduce any user-facing change?
No.
How was this patch tested?
Added appropriate unit tests to confirm that the config is effective:
STExpressionsSuiteWas this patch authored or co-authored using generative AI tooling?
No.