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
we try to integrate your project within our CI/CD build pipeline. One test uses an Upsert command (2nd) to update an existing entry, which was previously added with a first upsert command (1st).
When the 2nd Upsert statement is issued, we get this reply:
{HTTPFailure}Status code: 409 {"code":"Conflict","message":"Resource with specified id or name already exists."}
As far as I understand, Upsert should NEVER return an error like "already exists" since the entry should just be overwritten or inserted. The test runs fine when running it agains a local installation of the Azure CosmosDB Emulator (https://docs.microsoft.com/de-de/azure/cosmos-db/local-emulator).
I guess this is a bug?
The text was updated successfully, but these errors were encountered:
Hi,
we try to integrate your project within our CI/CD build pipeline. One test uses an Upsert command (2nd) to update an existing entry, which was previously added with a first upsert command (1st).
When the 2nd Upsert statement is issued, we get this reply:
{HTTPFailure}Status code: 409
{"code":"Conflict","message":"Resource with specified id or name already exists."}
As far as I understand, Upsert should NEVER return an error like "already exists" since the entry should just be overwritten or inserted. The test runs fine when running it agains a local installation of the Azure CosmosDB Emulator (https://docs.microsoft.com/de-de/azure/cosmos-db/local-emulator).
I guess this is a bug?
The text was updated successfully, but these errors were encountered: