AllowBulkExecution is internal for stable builds
See original GitHub issueCosmosClientOptions.AllowBulkExecution
is public for the preview build 3.2.0-preview2
, but internalized for the final version 3.2.0
. I’d like to avoid using preview. What is the reason for this conditional compilation?
Issue Analytics
- State:
- Created 4 years ago
- Comments:7 (6 by maintainers)
Top Results From Across the Web
CosmosClientOptions.AllowBulkExecution Property
Allows optimistic batching of requests to service. Setting this option might impact the latency of the operations. Hence this option is recommended for ......
Read more >A technical overview of Azure Cosmos DB | Azure Blog
Enable customers to elastically scale throughput and storage based on demand, globally. · Enable customers to build highly responsive, mission- ...
Read more >New Azure Cosmos DB Features to Boost Performance and ...
Microsoft has recently unveiled several new features for Azure Cosmos DB to enhance cost efficiency, boost performance, and increase ...
Read more >Package apache-airflow-providers-microsoft-azure
Fix where account url is build if not provided using login (account name) ... Allow and prefer non-prefixed extra fields for remaining azure...
Read more >@azure/storage-file-share | Yarn - Package Manager
Fast, reliable, and secure dependency management.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@SeanFeldman please take a look at this PR to update the changelog to make it a little bit clearer on how the preview versions work.
The preview features will not be included in the official release of the same version. A lot of the features in the SDK have changes in the Cosmos DB service. The changes to the service need to be ran for a while to verify the performance and stability of the new feature. We need to ship the SDK faster than the features are ready. To better explain how the versioning is currently working here is an example of the bulk feature.
Bulk is in 3.2.0-preview2 Bulk is not in 3.2.0 Bulk might be in 3.3.0 or it could still be a separate 3.3.0-preview package.
@Dave76 I think the best way to share your results is a github issue. That way everyone can see it.