Support DataLakeServiceClient for Azure Gen 2 Storage
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 211
- Forks
- 120
- PR merge metrics
- No merged PRs in 30d
Description
Currently, adlfs is using BlobServiceClient for both ADLS Gen 2 and Blob storage. Blob client is using blob apis underneath but if we want to use data lake apis currently there isn't an option. Can we support the client instance as input so that user can pass either BlobServiceClient or DataLakeServiceClient based on the usage?
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 tracing how adlfs currently creates or accepts BlobServiceClient instances, then compare the required Azure SDK client paths for BlobServiceClient and DataLakeServiceClient. Done means callers can provide either client type and the existing Blob and ADLS Gen 2 usage paths continue to work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, python
- Domain
- cloud
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100