lance-format / lance-format/lance-namespace-impls
Vended credentials for Unity Catalog
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 11
- Forks
- 13
- PR merge metrics
- No merged PRs in 30d
Description
For Lance tables hosted in Unity (both OSS and Databricks), the catalog can hold the table identity, metadata and location in storage. However, it gives not way of giving access. Users instead needs to handle authorization separately.
Possible solution
Most catalog implementations uses vended credentials for giving short living tokens for accessing the external storage. See example from Databricks: https://learn.microsoft.com/en-us/azure/databricks/external-access/credential-vending
This is available in the Unity API and could be used to read the data.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review the existing Unity Catalog implementation and the Unity API documentation linked in the issue, starting with Databricks' credential-vending example. Trace how the catalog currently resolves table locations for both OSS and Databricks. Done means reads can obtain short-lived credentials through Unity rather than requiring separate authorization handling.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- cloud, databases
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100