You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I created a local fork and make some changes to allow for IAM pass-through if you're using normal S3 credentials that duckdb already supports, and it works there. But I wouldn't really count on databricks making it where you can pull your blob storage credentials from their API since it may have more permissions than what Unity Catalog would allow the acting principal.
Super excited about this new UC integration!
However, since temporary-table-credentials is not working, currently I cannot read any table
Getting Error interacting with object store: Generic S3 error: Client error with status 403 Forbidden:
Thank you very much for the great work!
Shall we expect to have Databricks client unified authentication supported + profile support ?
The text was updated successfully, but these errors were encountered: