feat (azure): support for account in az:// URLs#403
Merged
Conversation
az:// URLs
kylebarron
reviewed
Jun 9, 2025
47c18ac to
a02b87c
Compare
kylebarron
approved these changes
Jun 13, 2025
Member
|
If you merge main, CI should be fixed from #404 |
Contributor
Author
|
@kylebarron can you please run the workflows again? |
Member
|
I'm not a maintainer myself and don't have permissions to enable workflows. |
Contributor
Author
|
Rebased w/ upstream to resolve clippy issues. All CI checks should now pass. |
tustvold
approved these changes
Jul 8, 2025
crepererum
pushed a commit
to crepererum/arrow-rs-object-store
that referenced
this pull request
Jul 10, 2025
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Which issue does this PR close?
Closes #285 .
Rationale for this change
When using a URL of type
az://container@account.dfs.core.windows.net/path-part/file, the account name wasn't parsed from the URL. It is now done.What changes are included in this PR?
The parser logic used for URL scheme
az://is now the same as that used forabfs://Are there any user-facing changes?
No. However, they can now use the scheme
az://just as they used to useabfs://