-
Notifications
You must be signed in to change notification settings - Fork 2.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Cosmos] work items for async preview #22043
Comments
Split proof sync client queries: #22237 - RELEASED IN b2 |
Split proof async client queries: #22261 - RELEASED IN b3 |
Deprecate |
Edit async client user agent to be different for ease of use when debugging: #22263 - RELEASED IN b2 |
Add warning to sync client's |
Transition into using python3 type hints for async client: #23933 |
GetAuthorizationMethod documentation should be removed and then made private with proper method naming: #22284 |
Remove support for Python2: #22475 - RELEASED IN b2 |
Move |
Undocument/ remove documentation around build_options, cosmos_client_connection, connection_retry_policy for both clients: #23945 |
This issue will be used to track work items that should be completed while the async client is in preview mode. Any item with a checkmark will have its PR as a comment below as well.
populate_query_metrics
flag if used in methods that don't need it and remove from documentationread_offer
in the sync api to align withread_throughput
renaming in async client (Cosmos no longer references Offers in public docs as opposed to Throughput - may confuse users trying to use these functionalities)build_options, cosmos_client_connection, connection_retry_policy
for both clients - objects need to be private. For this one, add samples to show how a user might pass in retry/ policy config values as opposed to object instanceGetAuthorizationHeader
documentation should be removed from sync client and then made private, also bring in method with proper naming to not create breaking changes.is_system_key
logic to be computed only once on container usage #23169 - RELEASED b4The text was updated successfully, but these errors were encountered: