Azure Table Client ListTablesSegmented

Question

When I use CloudTableClient.ListTableSegmented to retrieve the tables, I get a weird behaviour when I specify the max number of results to receive. I'm using version 2.0.3 of WindowsAzure.Storage.

This help reference says if I use 0 as maxResults, ListTablesSegmented should return the maximum possible number of results, up to 5000. When I use 0 as input the method throws an exception, saying the value should be positive greater than zero, and if I use 4999 or 5000 I get a StorageException with InvalidInput as error code. Everything runs smooth if I use for example 1000, or other values.

Am I doing anything wrong or anyone knows if this is a known bug? I didn't find it amongst the known issues.

Gaurav Mantri · Accepted Answer · 2013-01-21 14:08:22Z

2

There is an issue with the documentation. A single call to table service can return a maximum of 1000 entities (or tables). Please see here for more details: http://msdn.microsoft.com/en-us/library/windowsazure/dd179405.aspx. 5000 is applicable to blob storage (listing containers and blobs) and queues (listing queues).

answered Jan 21, 2013 at 14:08

Gaurav Mantri

137k17 gold badges247 silver badges282 bronze badges

Sign up to request clarification or add additional context in comments.

Collectives™ on Stack Overflow

Azure Table Client ListTablesSegmented

1 Answer 1

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

Comments

Your Answer

Sign up or log in

Post as a guest

Related