Enable native geospatial type support by default (#1446)

## 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.

---------

Signed-off-by: Sreekanth Vadigi <sreekanth.vadigi@databricks.com>

Author: sreekanth-db

NEXT_CHANGELOG.md

@@ -10,6 +10,8 @@
 
 3. **For DBSQL warehouses, metadata operations are now powered by SHOW SQL commands.** SQL Exec API mode already was powered by SHOW commands, now the same is true for Thrift server mode as well. To revert to native Thrift metadata RPCs, set `UseQueryForMetadata` to `0`.
 
+4. **Native geospatial type support (`GEOMETRY` and `GEOGRAPHY`) is now enabled by default.** `getObject()` now returns `IGeometry`/`IGeography` instances instead of EWKT strings. Set `EnableGeoSpatialSupport=0` to restore the previous behavior.
+
 ### Added
 
 ### Updated

src/main/java/com/databricks/jdbc/common/DatabricksJdbcUrlParams.java

@@ -131,7 +131,7 @@ public enum DatabricksJdbcUrlParams {
   ENABLE_GEOSPATIAL_SUPPORT(
       "EnableGeoSpatialSupport",
       "flag to enable native support of GEOMETRY and GEOGRAPHY data types",
-      "0"),
+      "1"),
   ROWS_FETCHED_PER_BLOCK(
       "RowsFetchedPerBlock",
       "The maximum number of rows that a query returns at a time.",

src/test/java/com/databricks/jdbc/api/impl/DatabricksConnectionContextTest.java

@@ -1618,11 +1618,11 @@ public void testGeospatialAndComplexBothDisabled() throws DatabricksSQLException
   }
 
   @Test
-  public void testGeospatialDefaultDisabled() throws DatabricksSQLException {
-    // Neither flag set — both default to disabled
+  public void testGeospatialDefaultEnabled() throws DatabricksSQLException {
+    // Neither flag set — geospatial defaults to enabled, complex datatypes to disabled
     IDatabricksConnectionContext ctx =
         DatabricksConnectionContext.parse(TestConstants.VALID_URL_1, properties);
-    assertFalse(ctx.isGeoSpatialSupportEnabled());
+    assertTrue(ctx.isGeoSpatialSupportEnabled());
     assertFalse(ctx.isComplexDatatypeSupportEnabled());
   }
 

src/test/java/com/databricks/jdbc/integration/fakeservice/tests/DataTypesIntegrationTests.java

@@ -361,9 +361,11 @@ void testGeospatialTypes() throws SQLException {
         rs, "ResultSet should not be null - GEOMETRY/GEOGRAPHY types may not be supported");
     ResultSetMetaData rsmd = rs.getMetaData();
 
-    // Validate metadata
-    assertEquals("STRING", rsmd.getColumnTypeName(2));
-    assertEquals("STRING", rsmd.getColumnTypeName(3));
+    // Validate metadata — geospatial support is enabled by default
+    // ST_GeomFromText without SRID → GEOMETRY(0); ST_GeogFromText defaults to WGS 84 →
+    // GEOGRAPHY(4326)
+    assertEquals("GEOMETRY(0)", rsmd.getColumnTypeName(2));
+    assertEquals("GEOGRAPHY(4326)", rsmd.getColumnTypeName(3));
 
     // Validate data
     int rowCount = 0;