Open neil-yechenwei opened 1 year ago
Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @pjohari-ms, @MehaKaushik, @zfoster, @kushagraThapar, @simorenoh, @simplynaveen20, @abinav2307.
Author: | neil-yechenwei |
---|---|
Assignees: | - |
Labels: | `Cosmos`, `Service Attention`, `needs-triage` |
Milestone: | - |
Recently, we found that the defaultConsistencyLevel property isn't set to the value defined in request payload while creating the restored CosmosDB Account. This issue happens around 2023-05-19. Previously it works fine with same repro steps,which means the defaultConsistencyLevel property is able to be set to the value defined in request payload while creating the restored CosmosDB Account. So I assume it's a regression issue. Could you take a look/fix this issue asap? Thanks in advance.
Repro steps:
Request Payload 1 - Create source CosmosDB Account:
Request Payload 2 - Create the restored CosmosDB Account based on above source CosmosDB Account:
API Response for the restored CosmosDB Account: