Say I have 2k partitions. I.E. 2k distinct partitions keys. All partitions have 3 guid rowkeys.
To illustrate:
Partition 1 - Guid 1(rowkey) - Guid 2(rowkey) - Guid 3(rowkey)
Partition 2 - Guid 4(rowkey) - Guid 5(rowkey) - Guid 6(rowkey)
.... etc etc.
If I were to do a query for an exact guid across all partitions. What sort of query performance would I be looking at? A direct retrieve or table scan?
More background info. I intend to have the following schema:
UserEntity
Partition Key - User Guid
Row Key - Username
OpenIdEntity
Partition Key - User Guid (Same as UserEntity)
Row Key - OpenId
Now, when a user logs in, I need to 1) find the open ID (select record with 1 distinct rowkey here, regardless of partition) 2) find username. (select record with 1 distinct partition key. table scan for a property or something. Since partition key is known and partition is small, the impact of table scan should be minimal)
My concern is step 1 being slow if the Azure Table Storage scans entire table to find 1 distinct rowkey.
Thanks in advance.