Skip to content
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

Expected layout and structure of Azure storage accounts should be documented #60

Closed
rtyler opened this issue Jan 9, 2021 · 2 comments
Closed
Labels
documentation Improvements or additions to documentation good first issue Good for newcomers storage/azure Azure Blog storage related

Comments

@rtyler
Copy link
Member

rtyler commented Jan 9, 2021

In order to use Delta Lake and Azure, the library expects the storage account to be configured with Azure Delta Lake Service Gen2 enabled, which is a non-default setting.

Some README or user-guide type documentation on how a Delta Table(s) should look in Azure, including the Azure configuration, would be beneficial for us to include!

@rtyler rtyler added documentation Improvements or additions to documentation good first issue Good for newcomers storage/azure Azure Blog storage related labels Jan 9, 2021
@drahnreb
Copy link

drahnreb commented May 6, 2021

Highly appreciated if this is documented. I haven't looked into the Rust code, but from a python perspective this is very opaque.

@roeap
Copy link
Collaborator

roeap commented Sep 2, 2022

With the adoption of object_store, we now use the blob api throughout, which is supported by Gen1 and Gen2 accounts. We do retain the if_not_exists functionality of course :).

@roeap roeap closed this as completed Sep 2, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation good first issue Good for newcomers storage/azure Azure Blog storage related
Projects
None yet
Development

No branches or pull requests

3 participants