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.

Sign up for GitHub

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

Jump to bottom

Support showonly in azdatalake in order to efficiently list directories #23852

Open
paulbrittain opened this issue Dec 9, 2024 · 3 comments
Open

Support showonly in azdatalake in order to efficiently list directories #23852

paulbrittain opened this issue Dec 9, 2024 · 3 comments
Assignees
@vibhansa-msft @tanyasethi-msft
Labels
customer-reported Issues that are reported by GitHub users external to the Azure organization. feature-request This issue requires a new behavior in the product in order be resolved. needs-team-attention Workflow: This issue needs attention from Azure service team or SDK team needs-team-triage Workflow: This issue needs the team to triage. Storage Storage Service (Queues, Blobs, Files)

Comments

@paulbrittain
Copy link

Feature Request

Following this issue in 2023, and this issue in 2022 no progress has been made in enabling this feature in 2024 (nearly 2025). The action of finding directories in a container is O(N) with using a standard pager that returns all paths. This is a problem when handling large numbers of files. The showonly REST API parameter should be supported in the Datalake sdk.

The showonly parameter is supported in the filesystem package of the datalake sdk only insofar as listing deleted paths, can a ListDirectoryPathsPager function please be added?
@github-actions github-actions bot added Client This issue points to a problem in the data-plane of the library. customer-reported Issues that are reported by GitHub users external to the Azure organization. needs-team-attention Workflow: This issue needs attention from Azure service team or SDK team question The issue doesn't require a change to the product in order to be resolved. Most issues start as that Service Attention Workflow: This issue is responsible by Azure service team. Storage Storage Service (Queues, Blobs, Files) labels Dec 9, 2024
@github-actions GitHub Actions
Copy link

github-actions bot commented Dec 9, 2024

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @xgithubtriage.

@jhendrixMSFT jhendrixMSFT added feature-request This issue requires a new behavior in the product in order be resolved. and removed question The issue doesn't require a change to the product in order to be resolved. Most issues start as that Service Attention Workflow: This issue is responsible by Azure service team. Client This issue points to a problem in the data-plane of the library. labels Dec 9, 2024
@github-actions github-actions bot added the needs-team-triage Workflow: This issue needs the team to triage. label Dec 9, 2024
@paulbrittain
Copy link
Author

Hi all, if a NewListDirectoryPathsPager filesystem function isn't prioritized, would the team be willing to accept a PR that adds it?

@tanyasethi-msft
Copy link
Member

Hi @paulbrittain Yes, please go ahead and make a contribution!

@tadelesh tadelesh added Client This issue points to a problem in the data-plane of the library. and removed Client This issue points to a problem in the data-plane of the library. labels Dec 13, 2024
@paulbrittain paulbrittain mentioned this issue Dec 16, 2024
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@vibhansa-msft vibhansa-msft

@tanyasethi-msft tanyasethi-msft

Labels
customer-reported Issues that are reported by GitHub users external to the Azure organization. feature-request This issue requires a new behavior in the product in order be resolved. needs-team-attention Workflow: This issue needs attention from Azure service team or SDK team needs-team-triage Workflow: This issue needs the team to triage. Storage Storage Service (Queues, Blobs, Files)
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@tadelesh @paulbrittain @jhendrixMSFT @vibhansa-msft @tanyasethi-msft