Merged
Conversation
…ssable items for massive recover failed operation
…le items and avoid to keep in memory all processed item for massive recover not notify operation
|
This PR exceeds the recommended size of 400 lines. Please make sure you are NOT addressing multiple issues with one PR. Note this PR might be rejected due to its size. |
|
Comment this PR with update_code to update |
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.



List of Changes
queryItemswithreadItemfor CosmosDB point searchMASSIVE_OPERATION_MAX_PROCESSABLE_ITEMS)Motivation and Context
PIDM-1661
Avoid Receipt Datastore pod failure for OOM on cron execution with large number of errors
Improve query performance and reduce RU consumption by switching from
queryItemstoreadItemfor CosmosDB point searchHow Has This Been Tested?
Screenshots (if appropriate):
Types of changes
Checklist: