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

get_blob_names in Azure Python SDK #25287

Closed
pathumd opened this issue Jul 19, 2022 · 1 comment
Closed

get_blob_names in Azure Python SDK #25287

pathumd opened this issue Jul 19, 2022 · 1 comment
Assignees
Labels
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. question The issue doesn't require a change to the product in order to be resolved. Most issues start as that Storage Storage Service (Queues, Blobs, Files)

Comments

@pathumd
Copy link

pathumd commented Jul 19, 2022

Hello,

Recently I've been building a Python application that acts as a search tool for an Azure storage account containing several containers. One container has nearly 1,100,000 blobs. When my script searches through this container, it takes nearly 23 minutes to fully complete.

I'm currently using the 'list_blobs' method to retrieve a generator containing all of the blobs in each container. However, this method seems to be very CPU intensive and ultimately is not ideal to use for e.g. a search tool.
I came across the 'Listing blobs names is very slow #19755' issue, and noticed that a new method called 'get_blob_names' is in the works which will be much faster in terms of getting blob names using the list_blobs method.

I was wondering if the get_blob_names method is available for use in the Azure Python SDK currently, and if not, when we can expect this method to be available for use. Thank you!

@ghost ghost added customer-reported Issues that are reported by GitHub users external to the Azure organization. question The issue doesn't require a change to the product in order to be resolved. Most issues start as that labels Jul 19, 2022
@xiangyan99 xiangyan99 added the needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. label Jul 19, 2022
@azure-sdk azure-sdk added Client This issue points to a problem in the data-plane of the library. needs-team-triage Workflow: This issue needs the team to triage. Storage Storage Service (Queues, Blobs, Files) labels Jul 19, 2022
@ghost ghost removed the needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. label Jul 19, 2022
@vincenttran-msft vincenttran-msft removed the needs-team-triage Workflow: This issue needs the team to triage. label Jul 19, 2022
@vincenttran-msft vincenttran-msft self-assigned this Jul 19, 2022
@vincenttran-msft
Copy link
Member

Hi @pathumd Pathum, thanks for your inquiry. Unfortunately, this functionality has not yet been implemented and I have no good on ETA on when this feature will be implemented and released. As you have pointed out, this issue seems to be the same request feature request as linked (issue #19755).

Therefore, I will continue with the closure of this issue as a duplicate. However, please post your personal inquiry as a follow up to that linked issue, so that any updates regarding this feature request can be centralized in one GitHub issue thread (and by posting your follow up in that thread, you will be notified anytime there is updates regarding this feature).
Thanks!

@github-actions github-actions bot locked and limited conversation to collaborators Apr 11, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
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. question The issue doesn't require a change to the product in order to be resolved. Most issues start as that Storage Storage Service (Queues, Blobs, Files)
Projects
None yet
Development

No branches or pull requests

4 participants