![]() ![]() ![]() If your query: RowKey = '123456789' then Azure Table storage can use the index on the rowkey to lookup the value pretty quick. If your query was just: RowKey = '123456789', Azure Table storage has to scan all the partitions (50 states) to find the matching RowKey.Īnother strategy might be one huge single partition with the rowkeys as social security numbers. In your query if you just pass PartitionKey='CA' & RowKey ='123456789' Azure Table Storage knows the partition to go to and the exact row in that partition. Let's look at two scenarios.Ī good partition strategy might be to have the state as the partition key. If you have a lot of partitions and you just specify the rowkey it will have to look up all partitions.įor example, say you stored social security numbers in table storage. ![]() ![]() Querying by the rowkey only would make sense if you had one partition (or very few partitions). Azure Table Storage (as of now) builds two indexes that makes lookups faster/fast which are the PartitionKey and Rowkey. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |