dependabot[bot] opened a new pull request, #3126: URL: https://github.com/apache/camel-kamelets/pull/3126
Bumps [com.databricks:databricks-jdbc](https://github.com/databricks/databricks-jdbc) from 3.4.4 to 3.4.5. <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.5</h2> <h3>Added</h3> <ul> <li>Implemented <code>Array.getResultSet()</code> and its overloads, returning one row per element (1-based index, value).</li> </ul> <h3>Updated</h3> <ul> <li>Updated bundled Netty (<code>netty-common</code> and <code>netty-buffer</code>) from 4.2.15.Final to 4.2.18.Final.</li> <li>Upgraded the bundled Guava dependency to 33.7.2-jre to address CVE-2026-102554.</li> <li>Removed automatic Thrift fallback after HTTP 307 SEA session creation failures. Redirect errors now propagate as connection errors without changing the selected protocol.</li> <li>Removed automatic Thrift fallback and the 24-hour SEA circuit breaker after HTTP 429 session creation failures. Rate-limit errors now propagate to the caller without changing routing for subsequent connections.</li> <li>Removed the <code>UseQueryForMetadata</code> connection property. It no longer forces the Thrift client, so connections eligible for SEA now use SEA with SQL metadata queries. Thrift connections use native metadata RPCs.</li> <li>SQL Execution API sessions open with warehouse URLs. Real-time sessions use warehouse URLs for session-owned statement operations and session close.</li> </ul> <h3>Fixed</h3> <ul> <li>Fixed <code>DatabricksArray.getBaseTypeName()</code> and <code>getBaseType()</code> to describe the array's element type (e.g. <code>INT</code> / <code>Types.INTEGER</code> for <code>ARRAY<INT></code>) per the <code>java.sql.Array</code> contract, instead of returning the full array type name and <code>Types.OTHER</code>. <code>ARRAY<MAP<...>></code> reports <code>Types.OTHER</code>, since its elements are <code>DatabricksMap</code> objects.</li> <li>Reject statement creation on closed connections before stale connection state can disable server-controlled features for subsequent connections.</li> <li>Report <code>CONNECTION_CLOSED</code> with vendor code <code>1010</code> from <code>DatabricksConnection</code> closed-connection checks, including statement preparation and <code>setClientInfo</code>.</li> <li>Report only explicitly supplied client-info properties when bulk updates fail on a closed connection.</li> <li>Fixed intermittent <code>NoHttpResponseException</code> ("failed to respond") on SQL Execution API connections that sat idle for about three minutes. The driver now closes SEA HTTP connections idle longer than <code>IdleHttpConnectionExpiry</code> (default 60 seconds) instead of reusing them, matching the Thrift client.</li> </ul> </blockquote> </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.5] - 2026-11-03</h2> <h3>Added</h3> <ul> <li>Implemented <code>Array.getResultSet()</code> and its overloads, returning one row per element (1-based index, value).</li> </ul> <h3>Updated</h3> <ul> <li>Updated bundled Netty (<code>netty-common</code> and <code>netty-buffer</code>) from 4.2.15.Final to 4.2.18.Final.</li> <li>Upgraded the bundled Guava dependency to 33.7.2-jre to address CVE-2026-102554.</li> <li>Removed automatic Thrift fallback after HTTP 307 SEA session creation failures. Redirect errors now propagate as connection errors without changing the selected protocol.</li> <li>Removed automatic Thrift fallback and the 24-hour SEA circuit breaker after HTTP 429 session creation failures. Rate-limit errors now propagate to the caller without changing routing for subsequent connections.</li> <li>Removed the <code>UseQueryForMetadata</code> connection property. It no longer forces the Thrift client, so connections eligible for SEA now use SEA with SQL metadata queries. Thrift connections use native metadata RPCs.</li> <li>SQL Execution API sessions open with warehouse URLs. Real-time sessions use warehouse URLs for session-owned statement operations and session close.</li> </ul> <h3>Fixed</h3> <ul> <li>Fixed <code>DatabricksArray.getBaseTypeName()</code> and <code>getBaseType()</code> to describe the array's element type (e.g. <code>INT</code> / <code>Types.INTEGER</code> for <code>ARRAY<INT></code>) per the <code>java.sql.Array</code> contract, instead of returning the full array type name and <code>Types.OTHER</code>. <code>ARRAY<MAP<...>></code> reports <code>Types.OTHER</code>, since its elements are <code>DatabricksMap</code> objects.</li> <li>Reject statement creation on closed connections before stale connection state can disable server-controlled features for subsequent connections.</li> <li>Report <code>CONNECTION_CLOSED</code> with vendor code <code>1010</code> from <code>DatabricksConnection</code> closed-connection checks, including statement preparation and <code>setClientInfo</code>.</li> <li>Report only explicitly supplied client-info properties when bulk updates fail on a closed connection.</li> <li>Fixed intermittent <code>NoHttpResponseException</code> ("failed to respond") on SQL Execution API connections that sat idle for about three minutes. The driver now closes SEA HTTP connections idle longer than <code>IdleHttpConnectionExpiry</code> (default 60 seconds) instead of reusing them, matching the Thrift client.</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/databricks/databricks-jdbc/commit/689b1769af45e04ddc91151a780db85e120db81d";><code>689b176</code></a> Prepare JDBC 3.4.5 release (<a href="https://redirect.github.com/databricks/databricks-jdbc/issues/1759";>#1759</a>)</li> <li><a href="https://github.com/databricks/databricks-jdbc/commit/ac299c66225c92b8cec385fcbf7b2de9bfb05778";><code>ac299c6</code></a> Close idle SEA HTTP connections before reuse (<a href="https://redirect.github.com/databricks/databricks-jdbc/issues/1758";>#1758</a>)</li> <li><a href="https://github.com/databricks/databricks-jdbc/commit/daa3e0fd0ecb141add3f0e46e805bdbe51b83c66";><code>daa3e0f</code></a> Upgrade Guava to 33.7.2 (<a href="https://redirect.github.com/databricks/databricks-jdbc/issues/1751";>#1751</a>)</li> <li><a href="https://github.com/databricks/databricks-jdbc/commit/e0f34a5a3a6c1c28a16ddb103e3cde958d000326";><code>e0f34a5</code></a> Fix flaky SEA chunk index test (<a href="https://redirect.github.com/databricks/databricks-jdbc/issues/1757";>#1757</a>)</li> <li><a href="https://github.com/databricks/databricks-jdbc/commit/a07536313f93c222ad1f885bc46eab95ecce68bf";><code>a075363</code></a> Remove SEA HTTP 307 Thrift fallback (<a href="https://redirect.github.com/databricks/databricks-jdbc/issues/1749";>#1749</a>)</li> <li><a href="https://github.com/databricks/databricks-jdbc/commit/a81aead5ca348fe4fff74777ad34cbdca44619cb";><code>a81aead</code></a> ci: update OSV-Scanner to v2.7.0 (<a href="https://redirect.github.com/databricks/databricks-jdbc/issues/1755";>#1755</a>)</li> <li><a href="https://github.com/databricks/databricks-jdbc/commit/625063cdeaf94fec486ad2f88da75296c163fc7f";><code>625063c</code></a> Reject statement creation on closed JDBC connections (<a href="https://redirect.github.com/databricks/databricks-jdbc/issues/1752";>#1752</a>)</li> <li><a href="https://github.com/databricks/databricks-jdbc/commit/68ca8be8a05b8dbb82189fa686618d4dc445fe71";><code>68ca8be</code></a> Bump netty.version from 4.2.15.Final to 4.2.18.Final (<a href="https://redirect.github.com/databricks/databricks-jdbc/issues/1671";>#1671</a>)</li> <li><a href="https://github.com/databricks/databricks-jdbc/commit/42cced36041ba66db7361b5caae3d30898007b63";><code>42cced3</code></a> Fix M2M private-key session replay fixture (<a href="https://redirect.github.com/databricks/databricks-jdbc/issues/1754";>#1754</a>)</li> <li><a href="https://github.com/databricks/databricks-jdbc/commit/8a291e451808f356bbde5f70568566f6700f0b47";><code>8a291e4</code></a> ci: Fix offline Maven setup for Engineer Bot follow-ups (<a href="https://redirect.github.com/databricks/databricks-jdbc/issues/1753";>#1753</a>)</li> <li>Additional commits viewable in <a href="https://github.com/databricks/databricks-jdbc/compare/v3.4.4...v3.4.5";>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]
