Skip to content

Update NEXT_CHANGELOG with detailed breaking changes for 3.4.1 #1449

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.

Sign up for GitHub

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

Merged
gopalldb merged 5 commits into from
May 19, 2026
Merged

Update NEXT_CHANGELOG with detailed breaking changes for 3.4.1 #1449

Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
5981464
Update changelog with detailed breaking changes for 3.4.1
gopalldb May 18, 2026
9b24970
Use [Unreleased] header format for NEXT_CHANGELOG
gopalldb May 18, 2026
151721f
Address review feedback on changelog structure and accuracy
gopalldb May 19, 2026
dc84f3c
Add DECIMAL precision/scale preservation as Updated note
gopalldb May 19, 2026
3f797f8
Merge branch 'main' into docs/update-changelog-breaking-changes
gopalldb May 19, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
35 changes: 30 additions & 5 deletions NEXT_CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,19 +2,44 @@

## [Unreleased]

### BREAKING CHANGES in 3.4.1
### BREAKING CHANGES in 3.4.1 — Metadata JDBC Spec Compliance
Copy link
Copy Markdown
Collaborator

@vikrantpuppala vikrantpuppala May 18, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

overall, i think we should stick to the added/updated/fixed structure that we have

Copy link
Copy Markdown
Collaborator Author

@gopalldb gopalldb May 19, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is a major change, so we wanted to highlight this explicitly.


1. **`getTables()`: Percent sign (`%`) in catalog argument is now treated as a literal character, not a wildcard.** Previously returned all tables; now returns zero rows unless a catalog named "%" exists. JDBC spec: catalog is an exact-match parameter, not a pattern. Migration: Pass `null` to search all catalogs.
This release unifies metadata behavior across Thrift and SQL Exec API backends
using SQL SHOW commands for all metadata operations on SQL warehouses. Several
non-spec-compliant behaviors have been corrected. Review the changes below before
upgrading. These changes do not affect metadata on All-Purpose Clusters.

2. **`getColumnTypeName()`: DECIMAL columns now return `"DECIMAL"` without precision/scale** (e.g., `"DECIMAL"` not `"DECIMAL(10,2)"`). Use `getPrecision()` and `getScale()` for numeric constraints. JDBC spec: `getColumnTypeName()` returns the base type name only.
* **`getTables`/`getColumns`/`getSchemas`: Catalog parameter is now treated as
an exact-match identifier per JDBC spec.** Passing `%` or wildcard patterns as
catalog previously returned results across all catalogs.
Use `null` to search all catalogs.

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`.
* **`getTables` with empty types array: Now returns zero rows per JDBC spec.**
Use `null` to return all types.

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.
* **`getSchemas`: Now includes `information_schema` in results.** Excludes
`global_temp` schema (previously returned by Thrift for all catalogs).

* **`getPrimaryKeys`/`getImportedKeys`/`getCrossReference` with non-existent
catalog, schema, or table: Now returns empty `ResultSet` instead of throwing
`SQLException`.**

* **`getImportedKeys` `UPDATE_RULE`/`DELETE_RULE`: Now returns `3` (`NO_ACTION`)
instead of `0` (`CASCADE`) for Thrift, and `3` instead of `null` for SEA.**
This reflects that Unity Catalog foreign keys are informational and non-enforced.

* **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
- Metadata operations now use SQL SHOW commands for both Thrift and SEA backends,
ensuring consistent behavior for SQL warehouses regardless of underlying
protocol. To revert to native Thrift metadata RPCs, set `UseQueryForMetadata=0`.

### Updated
- `getColumnTypeName()` for DECIMAL columns now preserves precision/scale suffix (e.g., `"DECIMAL(10,2)"`) consistently across both Thrift and SEA backends.
- `EnableGeoSpatialSupport` no longer requires `EnableComplexDatatypeSupport=1`. Geospatial types (GEOMETRY, GEOGRAPHY) can now be enabled independently of complex type support (ARRAY, MAP, STRUCT).
- Arrow schema deserialization failures (Thrift metadata path) now surface a dedicated driver error code `ARROW_SCHEMA_PARSING_ERROR` (vendor code `22000`) and a proper SQLSTATE `22000` (Data Exception) on the thrown `SQLException`, instead of the generic `RESULT_SET_ERROR` (1004) and the enum name as SQLSTATE. The exception message is unchanged.
- When a Statement is re-executed, the previous server-side operation is now explicitly closed before starting the new execution, preventing orphaned server-side operations when Statements are reused.
Expand Down
Loading