Preview of Bulk Stream #741
Merged
Conversation
This file contains 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
abhijitpai
reviewed
Aug 27, 2019
abhijitpai
reviewed
Aug 27, 2019
Microsoft.Azure.Cosmos/src/Resource/Container/ContainerCore.Items.cs
Outdated
Show resolved
Hide resolved
abhijitpai
reviewed
Sep 5, 2019
kirankumarkolli
approved these changes
Sep 5, 2019
|
/azp run |
|
Azure Pipelines successfully started running 2 pipeline(s). |
This was referenced Mar 8, 2021
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.
Description
This PR exposes the Bulk Streaming feature under the
PREVIEWflag. Working as an opt-in feature throughCosmosClientOptions.AllowBulkExecution(for a lack of a better name), orCosmosClientBuilder.WithBulkExecution, the SDK will send all point operations (Create, Read, Replace, Upsert, Delete) operations to theBulkAsyncContainerExecutorto be packed and sent as a single request for throughput optimized scenarios.Batch requests can return a MultiStatus Status Code, which might mean that some operations succeeded, but others failed (like in the case of throttling), so the
BatchExecutorRetryHandleris in place to retry individual operations that might have faced Throttles by evaluating throughResourceThrottleRetryPolicyand honoring theCosmosClientOptions.ConnectionPolicy.RetryOptionsconfiguration.This mode will squeeze the RU/s on the container, meaning that due to the increase of volume of data flow (versus doing these operations individually, which would take more time), it could incur into more 429s than sending them invididually, but if the RU budget is enough, the throughput (operations/sec) is much higher.
Type of change
Closing issues
Closes #584