Replace Operation Cosmos Db

Thanks Manish.

We are loading sequentially only (1 record create, then read the same document then replace/upsert as mentioned above all immediately though) and then second document for testing purpose. We noted that consistently throughout this test that 449 happens's only on 'replace' operations. Upsert positively gives a '200' OK response. And we ran the same test after deleting data many times and we see this behavior. So was checking regarding any atomicity or database specific (with respect to consistency etc) property differences with respect to replace and upsert operations? And if we receive 449s do we need to manually retry ( or a specific retry logic) those 449 response codes so the SDK will retry or had retried already? We did see 449's on Create operations before but thats not related this this discussion scope.

With Regards,

Nitin Rahim