Skip to content
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

Handle new SubStatusCodes for 413 on Bulk Read operations #21071

Closed
FabianMeiswinkel opened this issue Apr 29, 2021 · 1 comment
Closed

Handle new SubStatusCodes for 413 on Bulk Read operations #21071

FabianMeiswinkel opened this issue Apr 29, 2021 · 1 comment
Assignees
Labels
cosmos:v4-item Indicates this feature will be shipped as part of V4 release train Cosmos

Comments

@FabianMeiswinkel
Copy link
Member

Back in January Matias added retries on Bulk on 413 for Read operations Azure/azure-cosmos-dotnet-v3#2124 and added a tracking item for when the backend added a more specific substatus code on Batch API calls.

The backend added it in https://msdata.visualstudio.com/CosmosDB/_git/CosmosDB/pullrequest/523440?_a=files

That means that the retries can now be around the substatuscode: Azure/azure-cosmos-dotnet-v3#2390

This might needs to be ported to Java

@ghost ghost added the needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. label Apr 29, 2021
@FabianMeiswinkel FabianMeiswinkel added Cosmos and removed needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. labels Apr 29, 2021
@xinlian12 xinlian12 added the cosmos:v4-item Indicates this feature will be shipped as part of V4 release train label Jun 13, 2022
Copy link

Hi @FabianMeiswinkel, we deeply appreciate your input into this project. Regrettably, this issue has remained inactive for over 2 years, leading us to the decision to close it. We've implemented this policy to maintain the relevance of our issue queue and facilitate easier navigation for new contributors. If you still believe this topic requires attention, please feel free to create a new issue, referencing this one. Thank you for your understanding and ongoing support.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Mar 18, 2024
@github-actions github-actions bot locked and limited conversation to collaborators Mar 18, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
cosmos:v4-item Indicates this feature will be shipped as part of V4 release train Cosmos
Projects
None yet
Development

No branches or pull requests

2 participants