-
Notifications
You must be signed in to change notification settings - Fork 5.1k
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
The defaultConsistencyLevel property should be set to the value defined in request payload while creating the restored CosmosDB Account #24607
Comments
Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @pjohari-ms, @MehaKaushik, @zfoster, @kushagraThapar, @simorenoh, @simplynaveen20, @abinav2307. Issue DetailsRecently, 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:
|
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:
The text was updated successfully, but these errors were encountered: