current community

your communities

more stack exchange communities

company blog
Stack Exchange Inbox Reputation and Badges
tour help
Code Review Stack Exchange is a question and answer site for peer programmer code reviews. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top
up vote 2 down vote favorite

I want to check as fast as possible if an entity, based on PartitionKey and RowKey, exists in an Azure Table Storage.

I can do a standard TableOperation.Retrieve and check the result, like:

TableOperation retrieveOperation = TableOperation.Retrieve<CustomerEntity>("Smith", "Ben");
TableResult retrievedResult = table.Execute(retrieveOperation);

but that would return the complete entity.

By using a DynamicTableEntity I reduce the amount of data that is returned. More code, but I assume better...

public async Task<bool> EntityExists(string partitionKey, string rowKey)
{
    var tableQuery = new TableQuery<DynamicTableEntity>();
    tableQuery.FilterString = TableQuery.CombineFilters(
            TableQuery.GenerateFilterCondition("PartitionKey", QueryComparisons.Equal, paritionKey),
            TableOperators.And,
            TableQuery.GenerateFilterCondition("RowKey", QueryComparisons.Equal, rowKey));

    var dynamicTableEntities = await CloudTable.ExecuteQuerySegmentedAsync(tableQuery, null, TableRequestOptions, OperationContext);
    return dynamicTableEntities.Results.Any();
 }

Any suggestions/criticisms to my solution are welcome

share|improve this question
2  
There's not a ton of code here to critique, but what I'm seeing here looks fine to me, no major errors jump out at me, and you're using var when you should, although one might argue that you shouldn't be using it for var dynamicTableEntities =... because the type if not obvious from the right hand side of that expression. – Nick Udell May 27 '15 at 9:17
up vote 2 down vote

If I remember correctly, accessing a row by PartitionKey and RowKey is built to be the fastest operation you can do on an Azure Table Storage. The performance drawback of using a DynamicTableEntity probably isn't worth it unless the returned entity is really big.

I feel like you should stick to the Retrieve, but there's no better way to be sure than to profile both your solutions for performance to see which is better with your data.

Because there's nothing else to say about your code, from what I know, you have the 2 existing solutions in your hand. Figure the best one now :)

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.