-
Notifications
You must be signed in to change notification settings - Fork 330
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Azurite is incompatible with table API #2088
Comments
It looks the before issue is already resolved. Would you please share more details for this issue?
|
Repro'ed issue by running same setup using storage emulator and azurite. Adding details below: `
` Response from storage emulator for the below request (http://127.0.0.1:10002/devstoreaccount1/testAzInstances?$filter=PartitionKey%20eq%20%27fd069298416245df8bfbab27a3ed8d50%27&$select=ExecutionId%2CName%2CVersion%2COutput%2CCustomStatus%2CCreatedTime%2CLastUpdatedTime%2CCompletedTime%2CRuntimeStatus%2CScheduledStartTime%2CGeneration%2CPartitionKey%2CRowKey%2CTimestamp%2CETag) is as follows: Similar response for similar request (http://127.0.0.1:10002/devstoreaccount1/testAzInstances?$filter=PartitionKey%20eq%20%2751102896b2a445ae96bcba3d5334f020%27&$select=ExecutionId%2CName%2CVersion%2COutput%2CCustomStatus%2CCreatedTime%2CLastUpdatedTime%2CCompletedTime%2CRuntimeStatus%2CScheduledStartTime%2CGeneration%2CPartitionKey%2CRowKey%2CTimestamp%2CETag) from azurite: If we see, the response body is having some wrong values which are being complained by DTF with exception: Adding logs zip folder where AzurtieDebug is azurtie debug logs and respective pcap files from Storage emulator and azurite emulator |
Thanks for the responds! I have tried to run your program (with slightly change since build fail) on my machine, target both Azurite (version 3.25.1) and product Azure, both will fail with null reference. So would you please see if the issue can repro on product Azure on your side, and since Azurite has a Table Query refactor recently, would you please also see if the issue repro on latest Azurite version (3.25.1)? Product Azure:
Azurite 3.25.1:
|
Seems like this may be a problem of Azurite not working with the OLD table API, but it does work with the NEW table API. I was able to repro this problem -- "The metadata URI 'http://127.0.0.1:10002/devstoreaccount1/$metadata#Tables/@Element' is not valid for the expected payload kind 'Feed'" - with code using WindowsAzure.Storage 3.1.0.1. The code looks like this:
The query is as follows (I selected 4 columns from the table):
However, the following code, with the same query, using Azure.Data.Tables 12.8.1, works fine:
Issues like this are what finally got me to stop using the old Azure API and upgrade to the new one. (The upgrade is painful because the APIs are pretty different.) |
Which service(blob, file, queue, table) does this issue concern?
Table
Which version of the Azurite was used?
3.22.0
Where do you get Azurite? (npm, DockerHub, NuGet, Visual Studio Code Extension)
VisualStudio2022
What's the Node.js version?
NA
What problem was encountered?
Azurite seems to be somewhat incompatible with Table APi while storage emulator is. Since storage emulator is deprecated, it is not readily available on our build agents and azurite is not compatible.
Steps to reproduce the issue?
DurableTask framework is failing since table api is incompatible and this issue is same as previously mentioned issue #19 (Check ending discussion)
If possible, please provide the debug log using the -d parameter, replacing <pathtodebuglog> with an appropriate path for your OS, or review the instructions for docker containers:
Please be sure to remove any PII or sensitive information before sharing!
The debug log will log raw request headers and bodies, so that we can replay these against Azurite using REST and create tests to validate resolution.
Have you found a mitigation/solution?
The text was updated successfully, but these errors were encountered: