-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Compatibility with Azure OneLake (Fabric) #309
Comments
The original estimate was around 1 day if it were just changing/relaxing the regex. |
I've added the regex and built and uploaded/hosted a .jar for testing for the client |
URI format IS different from the one in the documentation it seems. Need to add this additional format to the experimental version. |
Will need to discuss with project maintainers if this is possible with current implementation. |
Updated epic in Jira, added time spent. |
Current state of affairs: We currently only support shared key authentication for ADLS Gen2 in storage-cloud-extension. The next steps if we take this route would be to add and test authentication using Entra ID (Azure AD) since this seems what's supported for OneLake: What can I offer to the customer right now: |
Meeting scheduled to talk with customer/ |
Progress on hold until July 16th |
Been discussed with the customer, ticket can be closed. There's more info in the actual Jira epic. |
Are the cloud storage extensions compatible with Azure OneLake?
According to https://learn.microsoft.com/en-us/fabric/onelake/onelake-api-parity the API is compatible to ADLS Gen2.
It would be good if we could verify that and also include it in the documentation.
The text was updated successfully, but these errors were encountered: