Improve error message when dealing with duplicate partition-/rowkey items in batch about azure-storage-net HOT 5 CLOSED

'Unexpected Response Code for Operation: 1' basically means that the operation at index 1 (i.e. the second operation) in the batch failed. The index of the failed operation is returned in the error thrown so it makes it easier for users to go and change the specific operation in the batch that failed.

You can get more information about the request that failed and the error by catching the StorageException and checking exception.RequestInformation.HttpStatusCode, exception.RequestInformation.ExtendedErrorInformation.ErrorCode and exception.RequestInformation.ExtendedErrorInformation.ErrorMessage. These should tell you that the request input is invalid.

The same information is also available in the OperationContext's last result if you use an OperationContext to track the request and use suitable method overloads that take in the OperationContext.

We will look at changing the error message in the future so it is less confusing. Thanks for the feedback!

from azure-storage-net.

We've made this message more clear in our 6.0.0 release -- it now reads: "Element i in the batch returned an unexpected response code." with i being the relevant index. Thanks for the feedback!

from azure-storage-net.

Why does it throw an error to begin with, or really why does it kill the batch? I've got a batch operation that is filled over and over again via a loop. Each individual entity is InsertOrMerge which shouldn't care if I put 100 entities in it with the same partition and row keys. There will be occasions when a duplicate will happen due to improper data entry, but I'm OK with that as long as the batch runs. Is there a way to code around this without having to dig through my batch and remove these entities? I'm asking all this because if I wasn't batching these it'd work fine, which is a pretty big con for batching. It seems like it'd make a lot more sense to provide a batch log that we could pull vs killing a batch and throwing an exception for something that would run outside of a batch.

from azure-storage-net.

This delightfully unhelpful error Microsoft.Azure.Cosmos.Table.StorageException: Element 0 in the batch returned an unexpected response code can also occur if you have a disallowed character in PartionKey or RowKey

@tbithell I investigated the problem by catching StorageException and within that iterate over TableOperation.InsertOrReplace which still returned a rather useless 400 BadRequest My problem item was a forward slash in RowKey.

from azure-storage-net.

Table support has moved to the CosmosDB NuGet package. Please follow up there.

https://www.nuget.org/packages/Microsoft.Azure.Cosmos.Table

from azure-storage-net.