dependabot[bot] opened a new pull request, #44194: URL: https://github.com/apache/superset/pull/44194
Updates the requirements on [databricks-sql-connector](https://github.com/databricks/databricks-sql-python) to permit the latest version. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/databricks/databricks-sql-python/releases";>databricks-sql-connector's releases</a>.</em></p> <blockquote> <h2>v4.5.0</h2> <ul> <li>Upgrade Databricks SQL Kernel to 1.0.0.</li> <li>Add JWT private-key M2M and Azure Entra authentication for kernel connections.</li> <li>Add <code>oauth_token_cache_enabled</code> for kernel U2M token caching.</li> <li>Forward kernel telemetry, socket timeout, OAuth, identity-federation, and row-limit settings.</li> <li>Preserve empty metadata filters and fix async statement telemetry.</li> <li>Lazy-load Apache Thrift for kernel and SEA connections.</li> <li>Deprecate SEA in favor of the kernel backend.</li> </ul> </blockquote> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/databricks/databricks-sql-python/blob/main/CHANGELOG.md";>databricks-sql-connector's changelog</a>.</em></p> <blockquote> <h1>4.5.0 (2026-09-01)</h1> <ul> <li>Upgrade Databricks SQL Kernel to 1.0.0.</li> <li>Add JWT private-key M2M and Azure Entra authentication for kernel connections.</li> <li>Add <code>oauth_token_cache_enabled</code> for kernel U2M token caching.</li> <li>Forward kernel telemetry, socket timeout, OAuth, identity-federation, and row-limit settings.</li> <li>Preserve empty metadata filters and fix async statement telemetry.</li> <li>Lazy-load Apache Thrift for kernel and SEA connections.</li> <li>Deprecate SEA in favor of the kernel backend.</li> </ul> <h1>4.4.0 (2026-07-22)</h1> <ul> <li><code>databricks/databricks-sql-python#798</code></li> <li>Fix: <code>REMOVE</code> staging operations no longer require <code>staging_allowed_local_path</code><code>databricks/databricks-sql-python#726</code></li> <li>Report <code>cursor.rowcount</code> for DML on the Thrift backend: INSERT/UPDATE/DELETE/MERGE now set <code>rowcount</code> to the server's affected-row count instead of the hardcoded <code>-1</code>; SELECT (and statements the server does not report a count for) still return <code>-1</code>. <code>executemany</code> aggregates the count across all parameter sets per PEP 249 (<a href="https://redirect.github.com/databricks/databricks-sql-python/issues/784";>#784</a>)</li> </ul> <h1>4.3.0 (2026-06-12)</h1> <ul> <li><strong>New: optional Rust kernel backend (<code>use_kernel=True</code>).</strong> Adds an alternative connection path backed by the native <a href="https://pypi.org/project/databricks-sql-kernel/";><code>databricks-sql-kernel</code></a> client (a Rust core exposed via PyO3), installable with the new <code>databricks-sql-connector[kernel]</code> extra. The kernel talks to Databricks over the <strong>SEA (Statement Execution API) HTTP transport</strong> — not Thrift — with CloudFetch and inline-Arrow result fetching, so <code>use_kernel=True</code> gives you a modern SEA-native client through the same DB-API surface. Supports PAT, OAuth M2M, and OAuth U2M auth. Requires Python >= 3.10 (the kernel wheel is <code>cp310-abi3</code>); on older interpreters the extra is a no-op and <code>use_kernel=True</code> raises a clear <code>ImportError</code>. The default backend remains Thrift — opt in per connection.</li> <li>Kernel backend behavior is aligned with the Thrift backend so application code works the same either way: consistent cursor-state tracking (<code>query_id</code> / <code>get_query_state</code>), metadata (catalogs/schemas/tables/columns with JDBC-style filter semantics and case-insensitive <code>table_types</code>), DML <code>rowcount</code>, server-sourced async execution state, sync <code>cancel()</code>, fail-loud staging/volume operations, and structured error context (SQLSTATE, diagnostic info). Kernel logs surface through Python <code>logging</code> under the <code>databricks.sql.kernel</code><code>databricks/databricks-sql-python#824</code><a href="https://redirect.github.com/databricks/databricks-sql-python/issues/825";>#825</a>, <a href="https://redirect.github.com/databricks/databricks-sql-python/issues/830";>#830</a>, <a href="https://redirect.github.com/databricks/databricks-sql-python/issues/838";>#838</a>, <a href="https://redirect.github.com/databricks/databricks-s ql-python/issues/839">#839</a> by <a href="https://github.com/vikrantpuppala";><code>@vikrantpuppala</code></a>)</li> <li><code>databricks/databricks-sql-python#840</code><a href="https://github.com/vikrantpuppala";><code>@vikrantpuppala</code></a>)</li> </ul> <h1>4.2.7 (2026-06-02)</h1> <ul> <li><code>databricks/databricks-sql-python#817</code><a href="https://github.com/msrathore-db";><code>@msrathore-db</code></a>)</li> <li><code>databricks/databricks-sql-python#814</code><a href="https://github.com/jprakash-db";><code>@jprakash-db</code></a>)</li> <li>Add <code>_retry_server_directed_only</code><code>databricks/databricks-sql-python#756</code><a href="https://github.com/sd-db";><code>@sd-db</code></a>)</li> <li><code>databricks/databricks-sql-python#796</code><a href="https://github.com/leoromanovsky";><code>@leoromanovsky</code></a>)</li> <li><code>databricks/databricks-sql-python#768</code><a href="https://github.com/moomindani";><code>@moomindani</code></a>)</li> <li><code>databricks/databricks-sql-python#781</code><a href="https://github.com/samikshya-db";><code>@samikshya-db</code></a>)</li> </ul> <h1>4.2.6 (2026-04-22)</h1> <ul> <li><code>databricks/databricks-sql-python#767</code><a href="https://github.com/msrathore-db";><code>@msrathore-db</code></a>)</li> <li><code>databricks/databricks-sql-python#776</code><a href="https://github.com/vikrantpuppala";><code>@vikrantpuppala</code></a>)</li> <li><code>databricks/databricks-sql-python#733</code><a href="https://github.com/Korijn";><code>@Korijn</code></a>)</li> <li><code>databricks/databricks-sql-python#740</code><a href="https://github.com/vikrantpuppala";><code>@vikrantpuppala</code></a>)</li> <li><code>databricks/databricks-sql-python#754</code><a href="https://github.com/sreekanth-db";><code>@sreekanth-db</code></a>)</li> <li><code>databricks/databricks-sql-python#751</code><a href="https://github.com/jprakash-db";><code>@jprakash-db</code></a>)</li> <li><code>databricks/databricks-sql-python#742</code><a href="https://github.com/Shubhambhusate";><code>@Shubhambhusate</code></a>)</li> <li><code>databricks/databricks-sql-python#749</code><a href="https://github.com/jiabin-hu";><code>@jiabin-hu</code></a>)</li> <li><code>databricks/databricks-sql-python#736</code><a href="https://github.com/jiabin-hu";><code>@jiabin-hu</code></a>)</li> </ul> <h1>4.2.5 (2026-02-09)</h1> <ul> <li><code>databricks/databricks-sql-python#735</code><a href="https://github.com/samikshya-db";><code>@samikshya-db</code></a>)</li> <li><code>databricks/databricks-sql-python#734</code><a href="https://github.com/msrathore-db";><code>@msrathore-db</code></a>)</li> </ul> <h1>4.2.4 (2026-01-07)</h1> <ul> <li><code>databricks/databricks-sql-python#723</code><a href="https://github.com/msrathore-db";><code>@msrathore-db</code></a>)</li> <li><code>databricks/databricks-sql-python#724</code><a href="https://github.com/nikhilsuri-db";><code>@nikhilsuri-db</code></a>)</li> </ul> <h1>4.2.3 (2025-12-18)</h1> <ul> <li><code>databricks/databricks-sql-python#720</code><a href="https://github.com/sreekanth-db";><code>@sreekanth-db</code></a>)</li> <li><code>databricks/databricks-sql-python#721</code><a href="https://github.com/sreekanth-db";><code>@sreekanth-db</code></a>)</li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/databricks/databricks-sql-python/commit/a22ac636d21655b55572f22a7a1e7ffd43e76c32";><code>a22ac63</code></a> Bump to version 4.5.0 (<a href="https://redirect.github.com/databricks/databricks-sql-python/issues/939";>#939</a>)</li> <li><a href="https://github.com/databricks/databricks-sql-python/commit/4c832f00676fe0a72534cc3749dd6f60eed64515";><code>4c832f0</code></a> Upgrade databricks-sql-kernel to 1.0.0 (<a href="https://redirect.github.com/databricks/databricks-sql-python/issues/938";>#938</a>)</li> <li><a href="https://github.com/databricks/databricks-sql-python/commit/5b5ab007c41d9d8c6f568b7cdf53ea8cd0e4c22a";><code>5b5ab00</code></a> fix(kernel): preserve empty metadata filters (<a href="https://redirect.github.com/databricks/databricks-sql-python/issues/933";>#933</a>)</li> <li><a href="https://github.com/databricks/databricks-sql-python/commit/1a7eb7409c93101a789fe5a11e290c8ab1dd9cbb";><code>1a7eb74</code></a> Forward telemetry parameters to the kernel binding (<a href="https://redirect.github.com/databricks/databricks-sql-python/issues/925";>#925</a>)</li> <li><a href="https://github.com/databricks/databricks-sql-python/commit/2ebc5e132865c314deb21c2ca7828eab404110be";><code>2ebc5e1</code></a> docs: fix two incorrect Kernel claims in CONNECTION_PARAMETERS.md (<a href="https://redirect.github.com/databricks/databricks-sql-python/issues/930";>#930</a>)</li> <li><a href="https://github.com/databricks/databricks-sql-python/commit/4ed862d8ae8fba04df157e4fbce61ede92e76a1e";><code>4ed862d</code></a> Lazy-load Apache Thrift so the SEA/kernel paths never import it (<a href="https://redirect.github.com/databricks/databricks-sql-python/issues/907";>#907</a>)</li> <li><a href="https://github.com/databricks/databricks-sql-python/commit/97fa9c1ce685b59f91a0ba3c6a45b9cc0e3a1c47";><code>97fa9c1</code></a> feat: add oauth_token_cache_enabled to control kernel U2M on-disk token cache...</li> <li><a href="https://github.com/databricks/databricks-sql-python/commit/17c7789d2d98f24b46358f82fb75744ecc7d6107";><code>17c7789</code></a> feat(kernel): forward socket timeout (<a href="https://redirect.github.com/databricks/databricks-sql-python/issues/931";>#931</a>)</li> <li><a href="https://github.com/databricks/databricks-sql-python/commit/c77f275bf023ec9f97f824c71ddb175b9ad551d7";><code>c77f275</code></a> Fix kernel async statement telemetry handle (<a href="https://redirect.github.com/databricks/databricks-sql-python/issues/923";>#923</a>)</li> <li><a href="https://github.com/databricks/databricks-sql-python/commit/c95ca3f918ce4afb478326eaa9b1f1c6af108ca3";><code>c95ca3f</code></a> feat(kernel): route Azure Entra auth (azure-sp-m2m + azure-oauth) through the...</li> <li>Additional commits viewable in <a href="https://github.com/databricks/databricks-sql-python/compare/v4.4.0...v4.5.0";>compare view</a></li> </ul> </details> <br /> 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
