You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is an inconsistency in the way Azurite serves queries that include inexistent properties. Azure Table Storage returns properties with null values, while Azurite does not include them in the payload.
[Informational] Azure-Core: Request [a12af699-92e1-49d3-ac1a-548547f6ba53] GET http://127.0.0.1:10002/devstoreaccount1/TableName(PartitionKey='PK',RowKey='RK')?$format=REDACTED&$select=NonNullProperty%2CInexistentProperty
User-Agent:azsdk-net-Data.Tables/12.8.3 (.NET 8.0.13; Microsoft Windows 10.0.22631)
Server:Azurite-Table/3.32.0
[Verbose] Azure-Core: Response [a12af699-92e1-49d3-ac1a-548547f6ba53] content: {"odata.metadata":"http://127.0.0.1:10002/devstoreaccount1/$metadata#TableName/@Element","odata.etag":"W/\"datetime'2025-02-28T06%3A54%3A16.4431620Z'\"","NonNullProperty":"something"}
That's what it looks like for Azure Table Storage:
Add entity:
[Informational] Azure-Core: Request [a1675057-f3d6-4f74-99be-d58a22ffd6f3] POST https://<REDACTED>.table.core.windows.net/TableName?$format=REDACTED
User-Agent:azsdk-net-Data.Tables/12.8.3 (.NET 8.0.13; Microsoft Windows 10.0.22631)
[Verbose] Azure-Core: Request [a1675057-f3d6-4f74-99be-d58a22ffd6f3] content: {"PartitionKey":"PK","RowKey":"RK","NonNullProperty":"something"}
Server:Windows-Azure-Table/1.0 Microsoft-HTTPAPI/2.0
Get entity requesting the inexsistent property:
[Informational] Azure-Core: Request [4e03764e-a8bd-4d3a-b762-1201272ed224] GET https://<REDACTED>.table.core.windows.net/TableName(PartitionKey='PK',RowKey='RK')?$format=REDACTED&$select=NonNullProperty%2CInexistentProperty
User-Agent:azsdk-net-Data.Tables/12.8.3 (.NET 8.0.13; Microsoft Windows 10.0.22631)
[Informational] Azure-Core: Response [4e03764e-a8bd-4d3a-b762-1201272ed224] 200 OK (00.1s)
Server:Windows-Azure-Table/1.0 Microsoft-HTTPAPI/2.0
[Verbose] Azure-Core: Response [4e03764e-a8bd-4d3a-b762-1201272ed224] content: {"odata.metadata":"https://<REDACTED>.table.core.windows.net/$metadata#TableName/@Element&$select=NonNullProperty,InexistentProperty","odata.etag":"W/\"datetime'2025-02-28T07%3A00%3A37.4437045Z'\"","InexistentProperty":null,"NonNullProperty":"something"}
To be honest, I would prefer if Table Storage behaved like Azurite :) In my scenario, I query for ~20 properties while only a few will have values. It means that the responses are unnecessarily large. If there is a way to tell Azure Table Storage to skip null properties, it would be much appreciated!
The text was updated successfully, but these errors were encountered:
There is an inconsistency in the way Azurite serves queries that include inexistent properties. Azure Table Storage returns properties with null values, while Azurite does not include them in the payload.
Add entity:
Get entity requesting the inexsistent property:
That's what it looks like for Azure Table Storage:
Add entity:
Get entity requesting the inexsistent property:
To be honest, I would prefer if Table Storage behaved like Azurite :) In my scenario, I query for ~20 properties while only a few will have values. It means that the responses are unnecessarily large. If there is a way to tell Azure Table Storage to skip null properties, it would be much appreciated!
The text was updated successfully, but these errors were encountered: