dependabot[bot] opened a new pull request, #2852: URL: https://github.com/apache/camel-kamelets/pull/2852
Bumps [com.databricks:databricks-jdbc](https://github.com/databricks/databricks-jdbc) from 3.3.3 to 3.4.1. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/databricks/databricks-jdbc/releases";>com.databricks:databricks-jdbc's releases</a>.</em></p> <blockquote> <h2>v3.4.1</h2> <h3>BREAKING CHANGES in 3.4.1</h3> <h4>Metadata JDBC Spec Compliance</h4> <p>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.</p> <ul> <li> <p><strong><code>getTables</code>/<code>getColumns</code>/<code>getSchemas</code>: Catalog parameter is now treated as an exact-match identifier per JDBC spec.</strong> Passing <code>%</code> or wildcard patterns as catalog previously returned results across all catalogs. Use <code>null</code> to search all catalogs.</p> </li> <li> <p><strong><code>getTables</code> with empty types array: Now returns zero rows per JDBC spec.</strong> Use <code>null</code> to return all types.</p> </li> <li> <p><strong><code>getSchemas</code>: Now includes <code>information_schema</code> in results.</strong> Excludes <code>global_temp</code> schema (previously returned by Thrift for all catalogs).</p> </li> <li> <p><strong><code>getPrimaryKeys</code>/<code>getImportedKeys</code>/<code>getCrossReference</code> with non-existent catalog, schema, or table: Now returns empty <code>ResultSet</code> instead of throwing <code>SQLException</code>.</strong></p> </li> <li> <p><strong><code>getImportedKeys</code> <code>UPDATE_RULE</code>/<code>DELETE_RULE</code>: Now returns <code>3</code> (<code>NO_ACTION</code>) instead of <code>0</code> (<code>CASCADE</code>) for Thrift, and <code>3</code> instead of <code>null</code> for SEA.</strong> This reflects that Unity Catalog foreign keys are informational and non-enforced.</p> </li> <li> <p><strong><code>PreparedStatement.setDate()</code> now sends parameter type as <code>DATE</code> instead of <code>TIMESTAMP</code>.</strong> Previously, <code>setDate()</code> incorrectly serialized the parameter type as TIMESTAMP due to a mapping bug. Server-side behavior is unchanged (Databricks accepts both), but applications that inspect parameter types may see the difference.</p> </li> </ul> <h4>Default Behavior Changes</h4> <ul> <li> <p><strong>Native geospatial type support (<code>GEOMETRY</code> and <code>GEOGRAPHY</code>) is now enabled by default.</strong> <code>getObject()</code> now returns <code>IGeometry</code>/<code>IGeography</code> instances instead of EWKT strings. Set <code>EnableGeoSpatialSupport=0</code> to restore the previous behavior.</p> </li> <li> <p><strong><code>EnableArrow</code> connection property is deprecated and ignored.</strong> Arrow serialization is now always enabled. Setting <code>EnableArrow=0</code> previously disabled Arrow and forced columnar/JSON inline results; this value is now ignored and a deprecation warning is logged. For JSON inline results with SEA, disable CloudFetch via <code>EnableQueryResultDownload=0</code>. Exception: on AIX platforms and PowerPC architectures (<code>os.arch</code> contains <code>ppc</code>), <code>EnableArrow</code> is still honoured and defaults to disabled due to known Arrow native library compatibility issues.</p> </li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/databricks/databricks-jdbc/blob/main/CHANGELOG.md";>com.databricks:databricks-jdbc's changelog</a>.</em></p> <blockquote> <h2>[v3.4.1] - 2026-05-25</h2> <h3>BREAKING CHANGES in 3.4.1</h3> <h4>Metadata JDBC Spec Compliance</h4> <p>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.</p> <ul> <li> <p><strong><code>getTables</code>/<code>getColumns</code>/<code>getSchemas</code>: Catalog parameter is now treated as an exact-match identifier per JDBC spec.</strong> Passing <code>%</code> or wildcard patterns as catalog previously returned results across all catalogs. Use <code>null</code> to search all catalogs.</p> </li> <li> <p><strong><code>getTables</code> with empty types array: Now returns zero rows per JDBC spec.</strong> Use <code>null</code> to return all types.</p> </li> <li> <p><strong><code>getSchemas</code>: Now includes <code>information_schema</code> in results.</strong> Excludes <code>global_temp</code> schema (previously returned by Thrift for all catalogs).</p> </li> <li> <p><strong><code>getPrimaryKeys</code>/<code>getImportedKeys</code>/<code>getCrossReference</code> with non-existent catalog, schema, or table: Now returns empty <code>ResultSet</code> instead of throwing <code>SQLException</code>.</strong></p> </li> <li> <p><strong><code>getImportedKeys</code> <code>UPDATE_RULE</code>/<code>DELETE_RULE</code>: Now returns <code>3</code> (<code>NO_ACTION</code>) instead of <code>0</code> (<code>CASCADE</code>) for Thrift, and <code>3</code> instead of <code>null</code> for SEA.</strong> This reflects that Unity Catalog foreign keys are informational and non-enforced.</p> </li> <li> <p><strong><code>PreparedStatement.setDate()</code> now sends parameter type as <code>DATE</code> instead of <code>TIMESTAMP</code>.</strong> Previously, <code>setDate()</code> incorrectly serialized the parameter type as TIMESTAMP due to a mapping bug. Server-side behavior is unchanged (Databricks accepts both), but applications that inspect parameter types may see the difference.</p> </li> </ul> <h4>Default Behavior Changes</h4> <ul> <li> <p><strong>Native geospatial type support (<code>GEOMETRY</code> and <code>GEOGRAPHY</code>) is now enabled by default.</strong> <code>getObject()</code> now returns <code>IGeometry</code>/<code>IGeography</code> instances instead of EWKT strings. Set <code>EnableGeoSpatialSupport=0</code> to restore the previous behavior.</p> </li> <li> <p><strong><code>EnableArrow</code> connection property is deprecated and ignored.</strong> Arrow serialization is now always enabled. Setting <code>EnableArrow=0</code> previously disabled Arrow and forced columnar/JSON inline results; this value is now ignored and a deprecation warning is logged. For JSON inline results with SEA, disable CloudFetch via <code>EnableQueryResultDownload=0</code>. Exception: on AIX platforms and PowerPC architectures (<code>os.arch</code> contains <code>ppc</code>), <code>EnableArrow</code> is still honoured and defaults to disabled due to known Arrow native library</p> </li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/databricks/databricks-jdbc/commit/ec4d74edc05a3a86278f593ba0d55bf5472b3ff2";><code>ec4d74e</code></a> v3.4.1 Bump (<a href="https://redirect.github.com/databricks/databricks-jdbc/issues/1467";>#1467</a>)</li> <li><a href="https://github.com/databricks/databricks-jdbc/commit/bc3d6c207bbe5085aae64236dcddfa241211916d";><code>bc3d6c2</code></a> Bump databricks-sdk-java from 0.69.0 to 0.106.0 (<a href="https://redirect.github.com/databricks/databricks-jdbc/issues/1465";>#1465</a>)</li> <li><a href="https://github.com/databricks/databricks-jdbc/commit/f01fe581bba8bc0849a773c153c6812f69b7c38e";><code>f01fe58</code></a> Add debug logging for connector-service feature flags request and response (#...</li> <li><a href="https://github.com/databricks/databricks-jdbc/commit/e1a2c53ddb75ac1d167feb14498d59ca130bf760";><code>e1a2c53</code></a> [PECOBLR-2321] Result Set Heartbeat / Keep-Alive for Ongoing Query Executions...</li> <li><a href="https://github.com/databricks/databricks-jdbc/commit/6da122a0de3b08abe549a5f0033d9058fc343c2d";><code>6da122a</code></a> Unify weekly + per-PR security scanning into a single workflow (<a href="https://redirect.github.com/databricks/databricks-jdbc/issues/1460";>#1460</a>)</li> <li><a href="https://github.com/databricks/databricks-jdbc/commit/c2ad803469ce236a0f1c2a53c0de42d268e7a917";><code>c2ad803</code></a> Fix PreparedStatement.getMetaData() crash for SQL type aliases (<a href="https://redirect.github.com/databricks/databricks-jdbc/issues/1289";>#1289</a>)</li> <li><a href="https://github.com/databricks/databricks-jdbc/commit/06476c81db0002ffce1e00d0dfc978abbc62e83b";><code>06476c8</code></a> Bump shaded bouncycastle and libthrift to clear remaining CVE findings (<a href="https://redirect.github.com/databricks/databricks-jdbc/issues/1461";>#1461</a>)</li> <li><a href="https://github.com/databricks/databricks-jdbc/commit/82700dbb5e2fd7f7ee4227900462b4455d126d5b";><code>82700db</code></a> Fix telemetry HTTP client socket leak preventing CRaC checkpoint (<a href="https://redirect.github.com/databricks/databricks-jdbc/issues/1333";>#1333</a>)</li> <li><a href="https://github.com/databricks/databricks-jdbc/commit/24699cf467a34f15a313d815a118dff6c3539f07";><code>24699cf</code></a> Deprecate EnableArrow — Arrow always enabled except on AIX/IBM Power (<a href="https://redirect.github.com/databricks/databricks-jdbc/issues/1450";>#1450</a>)</li> <li><a href="https://github.com/databricks/databricks-jdbc/commit/785981603b1e902198626bc6342370359fcf6529";><code>7859816</code></a> Fix DML misclassification for statements containing UNION/INTERSECT/EXCEPT (#...</li> <li>Additional commits viewable in <a href="https://github.com/databricks/databricks-jdbc/compare/v3.3.3...v3.4.1";>compare view</a></li> </ul> </details> <br /> [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
