Added Priority Based Execution for Sync and Async Clients #43917
+196
−1
Conversation
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
Contributor
There was a problem hiding this comment.
Pull Request Overview
This PR adds client-level priority configuration for Azure Cosmos DB clients (both sync and async), allowing users to set a default priority level for all requests made by a client. This complements the existing request-level priority feature, with request-level priority taking precedence when both are set.
- Added
priority_levelparameter toCosmosClientconstructors in both sync and async implementations - Client-level priority is stored in default headers and applied to all requests
- Comprehensive documentation and examples demonstrating client-level priority, request-level priority, and precedence behavior
Reviewed Changes
Copilot reviewed 7 out of 7 changed files in this pull request and generated no comments.
Show a summary per file
| File | Description |
|---|---|
| sdk/cosmos/azure-cosmos/azure/cosmos/_cosmos_client_connection.py | Implements client-level priority by adding priority_level parameter and storing it in default_headers |
| sdk/cosmos/azure-cosmos/azure/cosmos/aio/_cosmos_client_connection_async.py | Async implementation of client-level priority, mirroring the sync implementation |
| sdk/cosmos/azure-cosmos/tests/test_headers.py | Adds tests for client-level priority and request-level precedence in sync client |
| sdk/cosmos/azure-cosmos/tests/test_headers_async.py | Adds tests for client-level priority and request-level precedence in async client |
| sdk/cosmos/azure-cosmos/samples/examples.py | Demonstrates client-level priority usage and precedence with practical examples |
| sdk/cosmos/azure-cosmos/samples/examples_async.py | Demonstrates async client-level priority usage and precedence with practical examples |
Contributor
Author
|
/azp run python - cosmos - tests |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Member
|
/azp run python - cosmos - tests |
|
Azure Pipelines successfully started running 1 pipeline(s). |
simorenoh
requested changes
Nov 10, 2025
Member
simorenoh
left a comment
simorenoh
left a comment
There was a problem hiding this comment.
Some small comments but overall the changes seem to be good, thanks Andrew!
sdk/cosmos/azure-cosmos/azure/cosmos/_cosmos_client_connection.py
Outdated
Show resolved
Hide resolved
added 2 commits
November 11, 2025 10:04
Contributor
Author
|
/azp run python - cosmos - tests |
|
Azure Pipelines successfully started running 1 pipeline(s). |
simorenoh
approved these changes
Nov 11, 2025
simorenoh
reviewed
Nov 11, 2025
Co-authored-by: Simon Moreno <30335873+simorenoh@users.noreply.github.com>
andrewmathew1
changed the title
Contributor
Author
|
/azp run python - cosmos - tests |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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
Priority-based execution is a capability which allows users to specify priority for the request sent to Azure Cosmos DB. Based on the priority specified by the user, if there are more requests than the configured RU/s in a second, then Azure Cosmos DB will throttle low priority requests to allow high priority requests to execute. Previously this was only available at the request level now entire clients can be set to a low or high priority level. The request priority level will take precedence over the client priority level in case both are set.