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.
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.