feat(databricks): add AzureDatabricksDeltaClient via Unity Catalog credential vending - #19
Open
lukany wants to merge 3 commits into
Open
feat(databricks): add AzureDatabricksDeltaClient via Unity Catalog credential vending#19lukany wants to merge 3 commits into
lukany wants to merge 3 commits into
Conversation
…edential vending Read Unity Catalog tables directly from their underlying Azure storage using short-lived credentials vended by the temporary-table-credentials API, with no SQL warehouse or cluster. The client resolves a table by its full name, vends and caches an Azure user-delegation SAS, refreshes it before expiry, and returns a configured DeltaTableClient. The Databricks REST API is authenticated with a Microsoft Entra ID token (DefaultAzureCredential by default) via azure-core's pipeline. Adds a manual smoke script for verifying against a real workspace, guarded by an import test, and documents the credential-vending flow in the README.
lukany
marked this pull request as ready for review
June 16, 2026 19:25
pall-j
suggested changes
Jun 29, 2026
| uv add deltabridge | ||
| ``` | ||
|
|
||
| ## Usage |
Contributor
There was a problem hiding this comment.
Idea for new readme sections (from offline talk):
Options
1. Direct Storage Access
...
Example (Azure)
Example (Local)
2. Databricks Access (Unity Catalog)
Databricks tables can be accessed also through (1.) but recommended this approach is preferred in case of Databricks.
...
Example (Azure)
mbelak-dtml
reviewed
Jul 2, 2026
| on the schema (or parent catalog); | ||
| * the metastore must have external data access enabled; | ||
| * the table must not use row filters or column masks and must not be a | ||
| view - credential vending rejects those. |
Collaborator
There was a problem hiding this comment.
There are additional limitations:
- tables managed by Lakeflow Spark Declartive Pipelines are not supported (materialized views & streaming tables)
- shallow clones are not supported
- tables from a foreign metastore shared via Delta Sharing
Note: I tested this in late April 2026 using deltalake==1.5.1, might be outdated. However, I don't see any mention of any changes to these points in deltalake changelogs.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Read Unity Catalog tables directly from their underlying Azure storage using short-lived credentials vended by the temporary-table-credentials API, with no SQL warehouse or cluster. The client resolves a table by its full name, vends and caches an Azure user-delegation SAS, refreshes it before expiry, and returns a configured DeltaTableClient.
The Databricks REST API is authenticated with a Microsoft Entra ID token (DefaultAzureCredential by default) via azure-core's pipeline. Adds a manual smoke script for verifying against a real workspace, guarded by an import test, and documents the credential-vending flow in the README.