You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 12, 2023. It is now read-only.
I'm trying to understand what eventual plan is, or at least the guidance, on when to use bulk executor. In the docs I see articles like this: https://docs.microsoft.com/en-us/azure/cosmos-db/how-to-migrate-from-bulk-executor-library which encourage you to migrate away from using this library and instead use AllowBulkExecution, but what's unclear to me is if the bulk executor library uses some secret internal-only API that allows it to utilize more RUs than 'AllowBulkExecution' alone.
This image makes it seem like the Bulk API (which is not available on Serverless) is used by the Bulk Executor library, and the normal AllowBulkExecution just makes use of parallelism on the client-side.
So what is the recommendation? Is the Bulk API going away? Does AllowBulkExecution on the normal SDK utilize the bulk API for non-serverless instances?
The text was updated successfully, but these errors were encountered:
I think this entire repo could probably just be archived? Microsoft needs a strategy for bulk read/write in cosmos - this library is not the answer for that
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I'm trying to understand what eventual plan is, or at least the guidance, on when to use bulk executor. In the docs I see articles like this: https://docs.microsoft.com/en-us/azure/cosmos-db/how-to-migrate-from-bulk-executor-library which encourage you to migrate away from using this library and instead use
AllowBulkExecution
, but what's unclear to me is if the bulk executor library uses some secret internal-only API that allows it to utilize more RUs than 'AllowBulkExecution' alone.This image makes it seem like the
Bulk API
(which is not available on Serverless) is used by the Bulk Executor library, and the normalAllowBulkExecution
just makes use of parallelism on the client-side.So what is the recommendation? Is the
Bulk API
going away? DoesAllowBulkExecution
on the normal SDK utilize the bulk API for non-serverless instances?The text was updated successfully, but these errors were encountered: