Azure Table Storage - 501 Not Implemented

Question

I'm following this guide for using Azure Tables: https://learn.microsoft.com/en-us/dotnet/api/overview/azure/data.tables-readme-pre which uses the Azure.Data.Tables NuGet package.

I can successfully save a row and see it in the storage explorer within the Azure portal, however when trying to do a simple query, I'm getting back:

Unhandled exception. Azure.RequestFailedException: Service request failed.
Status: 501 (Not Implemented)

Content:
{"odata.error":{"code":"NotImplemented","message":{"lang":"en-US","value":"The requested operation is not implemented on the specified resource.\nRequestId:0137da3a-f002-0031-19
d6-5234ab000000\nTime:2021-05-27T08:59:39.8919922Z"}}}

My code for the query is:

    var entities = _tableClient
        .Query<TableEntity>(t => t.PartitionKey == PartitionKey)
        .ToList();

Answer 1

I ran in to this exact problem as well, and although it doesn't seem to be documented anywhere, the following worked for me:

var token = new DefaultAzureCredential();
var tableServiceClient = new TableServiceClient(new Uri($"https://{storageAccountName}.table.core.windows.net/"), token);
var client = tableServiceClient.GetTableClient(tableName);
var entities = client.Query<MyEntity>(filter: $"PartitionKey eq '{partKey}'");

I don't exactly understand why the direct creation of TableClient:

new TableClient(new Uri($"https://{storageAccountName}.table.core.windows.net/{tableName}"), tableName, token);

doesn't work, but going through TableServiceClient first worked for me. Give that a try.

Answer 2

The OP's problem was that they were using == instead of eq for their equality operator, as == is not one of the supported query comparison operators.

I had a different problem, but with the same error, so I thought I'd share my answer. I started receiving the same error after updating to the latest Azure.Data.Tables NuGet package, where I was getting an error like:

Status: 501 (Not Implemented)

ErrorCode: NotImplemented

Content: {"odata.error":{"code":"NotImplemented","message":{"lang":"en-US","value":"The requested operation is not implemented on the specified resource.\nRequestId:ce4208b5-b002-0001-63f9-59956d000000\nTime:2024-02-07T19:10:04.3685354Z"}}}

My issue was I using a boolean in my query filter like this:

filter += $" and (OperationSuccessful eq {parameters.Successful})";

Where parameters.Successful is a boolean. This resulted in a query filter like:

"(PartitionKey eq 'Some partition key') and (OperationSuccessful eq True)"

The NuGet package update seems to have introduced a breaking change where the query is now case-sensitive, so having "True" and "False" be capitalized breaks the OData query.

The solution was to update the code to:

filter += $" and (OperationSuccessful eq {parameters.Successful.ToString().ToLower()})";

Which results in the query looking like this instead:

"(PartitionKey eq 'Some partition key') and (OperationSuccessful eq true)"

It's a bit of a hassle, but it got things going again for me.

Answer 3

I had this issue in the java SDK when i created the client like so:

new TableClientBuilder()   
        .endpoint("https://{storageAccountName}.table.core.windows.net/{tableName}")
                .sasToken(sas)
                .tableName(tableName)
                .buildClient()

So what i did wrong was putting the table name as part of the endpoint and removing it stopped the exception.