Skip to content

Enable native geospatial type support by default#1445

Closed
sreekanth-db wants to merge 1 commit into
databricks:mainfrom
sreekanth-db:enable-geospatial-by-default
Closed

Enable native geospatial type support by default#1445
sreekanth-db wants to merge 1 commit into
databricks:mainfrom
sreekanth-db:enable-geospatial-by-default

Conversation

@sreekanth-db
Copy link
Copy Markdown
Collaborator

Summary

  • Changes EnableGeoSpatialSupport default from 0 to 1 so getObject() returns IGeometry/IGeography instances instead of raw EWKT strings out of the box.
  • Users can set EnableGeoSpatialSupport=0 to restore the previous behavior.

Test plan

  • Run GeospatialTests E2E suite (all 48 configurations) — verified locally, all pass
  • Verified default behavior across all 6 protocol/serialization/CloudFetch combinations: geospatial objects returned in all modes except Thrift+Inline (expected)
  • Existing tests unaffected since they explicitly set the flag

This pull request and its description were written by Isaac.

Change EnableGeoSpatialSupport default from "0" to "1" so getObject()
returns IGeometry/IGeography instances instead of raw EWKT strings.
Users can set EnableGeoSpatialSupport=0 to restore the previous behavior.

Co-authored-by: Isaac
Signed-off-by: Sreekanth Vadigi <sreekanth.vadigi@databricks.com>
@sreekanth-db sreekanth-db requested a review from gopalldb May 13, 2026 09:46
@sreekanth-db
Copy link
Copy Markdown
Collaborator Author

Recreating PR directly against upstream.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant