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

Add support for CloudTable.ExecuteQueryAsync #266

Closed
zsmorris opened this issue Oct 12, 2013 · 5 comments
Closed

Add support for CloudTable.ExecuteQueryAsync #266

zsmorris opened this issue Oct 12, 2013 · 5 comments
Labels
Service Attention Workflow: This issue is responsible by Azure service team. Storage Storage Service (Queues, Blobs, Files)

Comments

@zsmorris
Copy link

An ExecuteQueryAsync method on CloudTable would be very helpful.

ExecuteQuerySegmentedAsync exists but not as handy as ExecuteQuery. Something like https://github.com/glueckkanja/tasync/blob/master/StorageExtensions.cs but with full support for all query options (like Take).

@jharidas
Copy link

This is not considered best practice. Essentially to execute an entire query asynchronously would mean to follow all subsequent continuation tokens and store all resulting data in memory. In Azure Tables this could potentially mean 200 TB of data which is not practical. Once could conceivably create a helper method that simply executes N segmented operations until a given number of entities are returned, and such a method is simple enough do (i.e. an extension method ExecuteQueryForN) We will investigate possible alternatives in upcoming releases of the storage client library.

@zsmorris
Copy link
Author

Understood. But there's ultimately really no way to protect people from themselves, and having to write continuation logic all the time is a waste of time. Maybe just add a 'max entities to return' parameter to ExecuteQueryAsync, as you mentioned?

@jharidas
Copy link

We are going to take this as a feature request and investigate for a future release.

@joeg joeg closed this as completed Oct 23, 2013
@Cheesebaron
Copy link

Almost a year has passed and still nothing? Could you reconsider this?

@christav
Copy link

@Cheesebaron Azure storage library code and comments are at https://github.com/Azure/azure-storage-net. Could you open this discussion there?

@bsiegel bsiegel added the Service Attention Workflow: This issue is responsible by Azure service team. label Sep 26, 2018
@github-actions github-actions bot locked and limited conversation to collaborators Mar 29, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Service Attention Workflow: This issue is responsible by Azure service team. Storage Storage Service (Queues, Blobs, Files)
Projects
None yet
Development

No branches or pull requests

6 participants