lance-format / lance-format/lance
Support https URLs for Azure object storage
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 7.1k
- Forks
- 852
- Avg merge
- 3d 18h
- Merged PRs (30d)
- 272
Description
In our downstream repo we are supporting https to specify Azure storage like in this commit:
https://github.com/rerun-io/lance/commit/471b6a70085646668d30eaf6daf808875fbd51bc
The reason for this is that the official supported URL formatting for Azure uses https as described in this document:
This is problematic because if we did upstream this commit it would not work for any other custom storage that uses https URLs and is not very future proof.
I am not sure if the correct way forward is one of:
- Add
httpsjust for Azure - Do not support the official URL type for Azure and expect downstream users to switch URLs to
az - Add support for further processing of URLs, to do something like when it is
httpsto check for host patterns like*.blob.core.windows.netor similar
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the downstream commit 471b6a70085646668d30eaf6daf808875fbd51bc and the existing Azure storage URL handling. Check the official Azure URL format in the linked Microsoft documentation, then determine how support for https can avoid changing behavior for unrelated custom storage URLs. Done means the chosen approach supports official Azure https URLs without breaking other https-based storage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, rust
- Domain
- cloud
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100