{"author":"Microsoft Corporation","author_email":"askdocdb@microsoft.com","bugtrack_url":null,"classifiers":["Development Status :: 5 - Production/Stable","Intended Audience :: Developers","License :: OSI Approved :: MIT License","Natural Language :: English","Operating System :: OS Independent","Programming Language :: Python","Programming Language :: Python :: 3","Programming Language :: Python :: 3 :: Only","Programming Language :: Python :: 3.10","Programming Language :: Python :: 3.11","Programming Language :: Python :: 3.12","Programming Language :: Python :: 3.13","Programming Language :: Python :: 3.8","Programming Language :: Python :: 3.9"],"description":"# Azure Cosmos DB SQL API client library for Python\n\n## _Disclaimer_\n_Azure SDK Python packages support for Python 2.7 has ended 01 January 2022. For more information and questions, please refer to https://github.com/Azure/azure-sdk-for-python/issues/20691_\n\nAzure Cosmos DB is a globally distributed, multi-model database service that supports document, key-value, wide-column, and graph databases.\n\nUse the Azure Cosmos DB SQL API SDK for Python to manage databases and the JSON documents they contain in this NoSQL database service. High level capabilities are:\n\n* Create Cosmos DB **databases** and modify their settings\n* Create and modify **containers** to store collections of JSON documents\n* Create, read, update, and delete the **items** (JSON documents) in your containers\n* Query the documents in your database using **SQL-like syntax**\n\n[SDK source code][source_code]\n| [Package (PyPI)][cosmos_pypi]\n| [Package (Conda)](https://anaconda.org/microsoft/azure-cosmos/)\n| [API reference documentation][ref_cosmos_sdk]\n| [Product documentation][cosmos_docs]\n| [Samples][cosmos_samples]\n\n> This SDK is used for the [SQL API](https://docs.microsoft.com/azure/cosmos-db/sql-query-getting-started). For all other APIs, please check the [Azure Cosmos DB documentation](https://docs.microsoft.com/azure/cosmos-db/introduction) to evaluate the best SDK for your project.\n\n## Getting started\n\n### Important update on Python 2.x Support\n\nNew releases of this SDK won't support Python 2.x starting January 1st, 2022. Please check the [CHANGELOG](https://github.com/Azure/azure-sdk-for-python/blob/main/sdk/cosmos/azure-cosmos/CHANGELOG.md) for more information.\n\n### Prerequisites\n\n* Azure subscription - [Create a free account][azure_sub]\n* Azure [Cosmos DB account][cosmos_account] - SQL API\n* [Python 3.8+][python]\n\nIf you need a Cosmos DB SQL API account, you can create one with this [Azure CLI][azure_cli] command:\n\n```Bash\naz cosmosdb create --resource-group --name \n```\n\n### Install the package\n\n```bash\npip install azure-cosmos\n```\n\n#### Configure a virtual environment (optional)\n\nAlthough not required, you can keep your base system and Azure SDK environments isolated from one another if you use a virtual environment. Execute the following commands to configure and then enter a virtual environment with [venv][venv]:\n\n```Bash\npython3 -m venv azure-cosmosdb-sdk-environment\nsource azure-cosmosdb-sdk-environment/bin/activate\n```\n\n### Authenticate the client\n\nInteraction with Cosmos DB starts with an instance of the [CosmosClient][ref_cosmosclient] class. You need an **account**, its **URI**, and one of its **account keys** to instantiate the client object.\n\nUse the Azure CLI snippet below to populate two environment variables with the database account URI and its primary master key (you can also find these values in the Azure portal). The snippet is formatted for the Bash shell.\n\n```Bash\nRES_GROUP=\nACCT_NAME=\n\nexport ACCOUNT_URI=$(az cosmosdb show --resource-group $RES_GROUP --name $ACCT_NAME --query documentEndpoint --output tsv)\nexport ACCOUNT_KEY=$(az cosmosdb list-keys --resource-group $RES_GROUP --name $ACCT_NAME --query primaryMasterKey --output tsv)\n```\n\n### Create the client\n\nOnce you've populated the `ACCOUNT_URI` and `ACCOUNT_KEY` environment variables, you can create the [CosmosClient][ref_cosmosclient].\n\n```python\nfrom azure.cosmos import CosmosClient\n\nimport os\nURL = os.environ['ACCOUNT_URI']\nKEY = os.environ['ACCOUNT_KEY']\nclient = CosmosClient(URL, credential=KEY)\n```\n\n### AAD Authentication\n\nYou can also authenticate a client utilizing your service principal's AAD credentials and the azure identity package. \nYou can directly pass in the credentials information to ClientSecretCredential, or use the DefaultAzureCredential:\n```python\nfrom azure.cosmos import CosmosClient\nfrom azure.identity import ClientSecretCredential, DefaultAzureCredential\n\nimport os\nurl = os.environ['ACCOUNT_URI']\ntenant_id = os.environ['TENANT_ID']\nclient_id = os.environ['CLIENT_ID']\nclient_secret = os.environ['CLIENT_SECRET']\n\n# Using ClientSecretCredential\naad_credentials = ClientSecretCredential(\n tenant_id=tenant_id,\n client_id=client_id,\n client_secret=client_secret)\n\n# Using DefaultAzureCredential (recommended)\naad_credentials = DefaultAzureCredential()\n\nclient = CosmosClient(url, aad_credentials)\n```\nAlways ensure that the managed identity you use for AAD authentication has `readMetadata` permissions.
\nMore information on how to set up AAD authentication: [Set up RBAC for AAD authentication](https://docs.microsoft.com/azure/cosmos-db/how-to-setup-rbac)
\nMore information on allowed operations for AAD authenticated clients: [RBAC Permission Model](https://aka.ms/cosmos-native-rbac)\n\n## Key concepts\n\nOnce you've initialized a [CosmosClient][ref_cosmosclient], you can interact with the primary resource types in Cosmos DB:\n\n* [Database][ref_database]: A Cosmos DB account can contain multiple databases. When you create a database, you specify the API you'd like to use when interacting with its documents: SQL, MongoDB, Gremlin, Cassandra, or Azure Table. Use the [DatabaseProxy][ref_database] object to manage its containers.\n\n* [Container][ref_container]: A container is a collection of JSON documents. You create (insert), read, update, and delete items in a container by using methods on the [ContainerProxy][ref_container] object.\n\n* Item: An Item is the dictionary-like representation of a JSON document stored in a container. Each Item you add to a container must include an `id` key with a value that uniquely identifies the item within the container.\n\nFor more information about these resources, see [Working with Azure Cosmos databases, containers and items][cosmos_resources].\n\n\n## How to use `enable_cross_partition_query`\n\nThe keyword-argument `enable_cross_partition_query` accepts 2 options: `None` (default) or `True`.\n\n## Note on using queries by id\n\nWhen using queries that try to find items based on an **id** value, always make sure you are passing in a string type variable. Azure Cosmos DB only allows string id values and if you use any other datatype, this SDK will return no results and no error messages.\n\n## Note on client consistency levels\n\nAs of release version 4.3.0b3, if a user does not pass in an explicit consistency level to their client initialization,\ntheir client will use their database account's default level. Previously, the default was being set to `Session` consistency.\nIf for some reason you'd like to keep doing this, you can change your client initialization to include the explicit parameter for this like shown:\n```python\nfrom azure.cosmos import CosmosClient\n\nimport os\nURL = os.environ['ACCOUNT_URI']\nKEY = os.environ['ACCOUNT_KEY']\nclient = CosmosClient(URL, credential=KEY, consistency_level='Session')\n```\n\n## Limitations\n\nCurrently, the features below are **not supported**. For alternatives options, check the **Workarounds** section below.\n\n### Data Plane Limitations:\n\n* Group By queries\n* Queries with COUNT from a DISTINCT subquery: SELECT COUNT (1) FROM (SELECT DISTINCT C.ID FROM C)\n* Direct TCP Mode access\n* Continuation token support for aggregate cross-partition queries like sorting, counting, and distinct.\nStreamable queries like `SELECT * FROM WHERE` *do* support continuation tokens.\n* Change Feed: Processor\n* Change Feed: Read multiple partitions key values\n* Cross-partition ORDER BY for mixed types\n* Enabling diagnostics for async query-type methods\n\n### Control Plane Limitations:\n\n* Get CollectionSizeUsage, DatabaseUsage, and DocumentUsage metrics\n* Get the connection string\n* Get the minimum RU/s of a container\n\n## Workarounds\n\n### Control Plane Limitations Workaround\n\nTypically, you can use [Azure Portal](https://portal.azure.com/), [Azure Cosmos DB Resource Provider REST API](https://docs.microsoft.com/rest/api/cosmos-db-resource-provider), [Azure CLI](https://docs.microsoft.com/cli/azure/azure-cli-reference-for-cosmos-db) or [PowerShell](https://docs.microsoft.com/azure/cosmos-db/manage-with-powershell) for the control plane unsupported limitations.\n\n### Using The Async Client as a Workaround to Bulk\nWhile the SDK supports transactional batch, support for bulk requests is not yet implemented in the Python SDK. You can use the async client along with this [concurrency sample][cosmos_concurrency_sample] we have developed as a reference for a possible workaround. \n>[WARNING]\n> Using the asynchronous client for concurrent operations like shown in this sample will consume a lot of RUs very fast. We **strongly recommend** testing this out against the cosmos emulator first to verify your code works well and avoid incurring charges.\n\n\n\n## Boolean Data Type\n\nWhile the Python language [uses](https://docs.python.org/3/library/stdtypes.html?highlight=boolean#truth-value-testing) \"True\" and \"False\" for boolean types, Cosmos DB [accepts](https://docs.microsoft.com/azure/cosmos-db/sql-query-is-bool) \"true\" and \"false\" only. In other words, the Python language uses Boolean values with the first uppercase letter and all other lowercase letters, while Cosmos DB and its SQL language use only lowercase letters for those same Boolean values. How to deal with this challenge?\n\n* Your JSON documents created with Python must use \"True\" and \"False\", to pass the language validation. The SDK will convert it to \"true\" and \"false\" for you. Meaning that \"true\" and \"false\" is what will be stored in Cosmos DB.\n* If you retrieve those documents with the Cosmos DB Portal's Data Explorer, you will see \"true\" and \"false\".\n* If you retrieve those documents with this Python SDK, \"true\" and \"false\" values will be automatically converted to \"True\" and \"False\".\n\n## SQL Queries x FROM Clause Subitems\n\nThis SDK uses the [query_items](https://docs.microsoft.com/python/api/azure-cosmos/azure.cosmos.containerproxy?preserve-view=true&view=azure-python#query-items-query--parameters-none--partition-key-none--enable-cross-partition-query-none--max-item-count-none--enable-scan-in-query-none--populate-query-metrics-none----kwargs-) method to submit SQL queries to Azure Cosmos DB.\n\nCosmos DB SQL language allows you to [get subitems by using the FROM clause](https://docs.microsoft.com/azure/cosmos-db/sql-query-from#get-subitems-by-using-the-from-clause), to reduce the source to a smaller subset. As an example, you can use `select * from Families.children` instead of `select * from Families`. But please note that:\n\n* For SQL queries using the `query_items` method, this SDK demands that you specify the `partition_key` or use the `enable_cross_partition_query` flag.\n* If you are getting subitems and specifying the `partition_key`, please make sure that your partition key is included in the subitems, which is not true for most of the cases.\n\n## Max Item Count\n\nThis is a parameter of the query_items method, an integer indicating the maximum number of items to be returned per page. The `None` value can be specified to let the service determine the optimal item count. This is the recommended configuration value, and the default behavior of this SDK when it is not set.\n\n## Examples\n\nThe following sections provide several code snippets covering some of the most common Cosmos DB tasks, including:\n\n* [Create a database](#create-a-database \"Create a database\")\n* [Create a container](#create-a-container \"Create a container\")\n* [Create an analytical store enabled container](#create-an-analytical-store-enabled-container \"Create a container\")\n* [Get an existing container](#get-an-existing-container \"Get an existing container\")\n* [Insert data](#insert-data \"Insert data\")\n* [Delete data](#delete-data \"Delete data\")\n* [Query the database](#query-the-database \"Query the database\")\n* [Get database properties](#get-database-properties \"Get database properties\")\n* [Get database and container throughputs](#get-database-and-container-throughputs \"Get database and container throughputs\")\n* [Modify container properties](#modify-container-properties \"Modify container properties\")\n* [Using the asynchronous client](#using-the-asynchronous-client \"Using the asynchronous client\")\n\n### Create a database\n\nAfter authenticating your [CosmosClient][ref_cosmosclient], you can work with any resource in the account. The code snippet below creates a SQL API database, which is the default when no API is specified when [create_database][ref_cosmosclient_create_database] is invoked.\n\n```python\nfrom azure.cosmos import CosmosClient, exceptions\nimport os\n\nURL = os.environ['ACCOUNT_URI']\nKEY = os.environ['ACCOUNT_KEY']\nclient = CosmosClient(URL, credential=KEY)\nDATABASE_NAME = 'testDatabase'\ntry:\n database = client.create_database(DATABASE_NAME)\nexcept exceptions.CosmosResourceExistsError:\n database = client.get_database_client(DATABASE_NAME)\n```\n\n### Create a container\n\nThis example creates a container with default settings. If a container with the same name already exists in the database (generating a `409 Conflict` error), the existing container is obtained instead.\n\n```python\nfrom azure.cosmos import CosmosClient, PartitionKey, exceptions\nimport os\n\nURL = os.environ['ACCOUNT_URI']\nKEY = os.environ['ACCOUNT_KEY']\nclient = CosmosClient(URL, credential=KEY)\nDATABASE_NAME = 'testDatabase'\ndatabase = client.get_database_client(DATABASE_NAME)\nCONTAINER_NAME = 'products'\n\ntry:\n container = database.create_container(id=CONTAINER_NAME, partition_key=PartitionKey(path=\"/productName\"))\nexcept exceptions.CosmosResourceExistsError:\n container = database.get_container_client(CONTAINER_NAME)\nexcept exceptions.CosmosHttpResponseError:\n raise\n```\n\n### Create an analytical store enabled container\n\nThis example creates a container with [Analytical Store](https://docs.microsoft.com/azure/cosmos-db/analytical-store-introduction) enabled, for reporting, BI, AI, and Advanced Analytics with [Azure Synapse Link](https://docs.microsoft.com/azure/cosmos-db/synapse-link).\n\nThe options for analytical_storage_ttl are:\n\n+ 0 or Null or not informed: Not enabled.\n+ -1: The data will be stored infinitely.\n+ Any other number: the actual ttl, in seconds.\n\n\n```python\nCONTAINER_NAME = 'products'\ntry:\n container = database.create_container(id=CONTAINER_NAME, partition_key=PartitionKey(path=\"/productName\"),analytical_storage_ttl=-1)\nexcept exceptions.CosmosResourceExistsError:\n container = database.get_container_client(CONTAINER_NAME)\nexcept exceptions.CosmosHttpResponseError:\n raise\n```\n\nThe preceding snippets also handle the [CosmosHttpResponseError][ref_httpfailure] exception if the container creation failed. For more information on error handling and troubleshooting, see the [Troubleshooting](#troubleshooting \"Troubleshooting\") section.\n\n### Get an existing container\n\nRetrieve an existing container from the database:\n\n```python\nfrom azure.cosmos import CosmosClient\nimport os\n\nURL = os.environ['ACCOUNT_URI']\nKEY = os.environ['ACCOUNT_KEY']\nclient = CosmosClient(URL, credential=KEY)\nDATABASE_NAME = 'testDatabase'\ndatabase = client.get_database_client(DATABASE_NAME)\nCONTAINER_NAME = 'products'\ncontainer = database.get_container_client(CONTAINER_NAME)\n```\n\n### Insert data\n\nTo insert items into a container, pass a dictionary containing your data to [ContainerProxy.upsert_item][ref_container_upsert_item]. Each item you add to a container must include an `id` key with a value that uniquely identifies the item within the container.\n\nThis example inserts several items into the container, each with a unique `id`:\n\n```python\nfrom azure.cosmos import CosmosClient\nimport os\n\nURL = os.environ['ACCOUNT_URI']\nKEY = os.environ['ACCOUNT_KEY']\nclient = CosmosClient(URL, credential=KEY)\nDATABASE_NAME = 'testDatabase'\ndatabase = client.get_database_client(DATABASE_NAME)\nCONTAINER_NAME = 'products'\ncontainer = database.get_container_client(CONTAINER_NAME)\n\nfor i in range(1, 10):\n container.upsert_item({\n 'id': 'item{0}'.format(i),\n 'productName': 'Widget',\n 'productModel': 'Model {0}'.format(i)\n }\n )\n```\n\n### Delete data\n\nTo delete items from a container, use [ContainerProxy.delete_item][ref_container_delete_item]. The SQL API in Cosmos DB does not support the SQL `DELETE` statement.\n\n```python\nfrom azure.cosmos import CosmosClient\nimport os\n\nURL = os.environ['ACCOUNT_URI']\nKEY = os.environ['ACCOUNT_KEY']\nclient = CosmosClient(URL, credential=KEY)\nDATABASE_NAME = 'testDatabase'\ndatabase = client.get_database_client(DATABASE_NAME)\nCONTAINER_NAME = 'products'\ncontainer = database.get_container_client(CONTAINER_NAME)\n\nfor item in container.query_items(\n query='SELECT * FROM products p WHERE p.productModel = \"Model 2\"',\n enable_cross_partition_query=True):\n container.delete_item(item, partition_key='Widget')\n```\n\n> NOTE: If you are using partitioned collection, the value of the `partitionKey` in the example code above, should be set to the value of the partition key for this particular item, not the name of the partition key column in your collection. This holds true for both point reads and deletes.\n\n### Query the database\n\nA Cosmos DB SQL API database supports querying the items in a container with [ContainerProxy.query_items][ref_container_query_items] using SQL-like syntax.\n\nThis example queries a container for items with a specific `id`:\n\n```python\nfrom azure.cosmos import CosmosClient\nimport os\n\nURL = os.environ['ACCOUNT_URI']\nKEY = os.environ['ACCOUNT_KEY']\nclient = CosmosClient(URL, credential=KEY)\nDATABASE_NAME = 'testDatabase'\ndatabase = client.get_database_client(DATABASE_NAME)\nCONTAINER_NAME = 'products'\ncontainer = database.get_container_client(CONTAINER_NAME)\n\n# Enumerate the returned items\nimport json\nfor item in container.query_items(\n query='SELECT * FROM mycontainer r WHERE r.id=\"item3\"',\n enable_cross_partition_query=True):\n print(json.dumps(item, indent=True))\n```\n\n> NOTE: Although you can specify any value for the container name in the `FROM` clause, we recommend you use the container name for consistency.\n\nPerform parameterized queries by passing a dictionary containing the parameters and their values to [ContainerProxy.query_items][ref_container_query_items]:\n\n```python\ndiscontinued_items = container.query_items(\n query='SELECT * FROM products p WHERE p.productModel = @model',\n parameters=[\n dict(name='@model', value='Model 7')\n ],\n enable_cross_partition_query=True\n)\nfor item in discontinued_items:\n print(json.dumps(item, indent=True))\n```\n\nFor more information on querying Cosmos DB databases using the SQL API, see [Query Azure Cosmos DB data with SQL queries][cosmos_sql_queries].\n\n### Get database properties\n\nGet and display the properties of a database:\n\n```python\nfrom azure.cosmos import CosmosClient\nimport os\nimport json\n\nURL = os.environ['ACCOUNT_URI']\nKEY = os.environ['ACCOUNT_KEY']\nclient = CosmosClient(URL, credential=KEY)\nDATABASE_NAME = 'testDatabase'\ndatabase = client.get_database_client(DATABASE_NAME)\nproperties = database.read()\nprint(json.dumps(properties))\n```\n\n### Get database and container throughputs\n\nGet and display the throughput values of a database and of a container with dedicated throughput:\n\n```python\nfrom azure.cosmos import CosmosClient\nimport os\nimport json\n\nURL = os.environ['ACCOUNT_URI']\nKEY = os.environ['ACCOUNT_KEY']\nclient = CosmosClient(URL, credential=KEY)\n\n# Database\nDATABASE_NAME = 'testDatabase'\ndatabase = client.get_database_client(DATABASE_NAME)\ndb_offer = database.get_throughput()\nprint('Found Offer \\'{0}\\' for Database \\'{1}\\' and its throughput is \\'{2}\\''.format(db_offer.properties['id'], database.id, db_offer.properties['content']['offerThroughput']))\n\n# Container with dedicated throughput only. Will return error \"offer not found\" for containers without dedicated throughput\nCONTAINER_NAME = 'testContainer'\ncontainer = database.get_container_client(CONTAINER_NAME)\ncontainer_offer = container.get_throughput()\nprint('Found Offer \\'{0}\\' for Container \\'{1}\\' and its throughput is \\'{2}\\''.format(container_offer.properties['id'], container.id, container_offer.properties['content']['offerThroughput']))\n```\n\n\n### Modify container properties\n\nCertain properties of an existing container can be modified. This example sets the default time to live (TTL) for items in the container to 10 seconds:\n\n```python\nfrom azure.cosmos import CosmosClient, PartitionKey\nimport os\nimport json\n\nURL = os.environ['ACCOUNT_URI']\nKEY = os.environ['ACCOUNT_KEY']\nclient = CosmosClient(URL, credential=KEY)\nDATABASE_NAME = 'testDatabase'\ndatabase = client.get_database_client(DATABASE_NAME)\nCONTAINER_NAME = 'products'\ncontainer = database.get_container_client(CONTAINER_NAME)\n\ndatabase.replace_container(\n container,\n partition_key=PartitionKey(path=\"/productName\"),\n default_ttl=10,\n)\n# Display the new TTL setting for the container\ncontainer_props = container.read()\nprint(json.dumps(container_props['defaultTtl']))\n```\n\nFor more information on TTL, see [Time to Live for Azure Cosmos DB data][cosmos_ttl].\n\n### Using item point operation response headers\n\nResponse headers include metadata information from the executed operations like `etag`, which allows for optimistic concurrency scenarios, or `x-ms-request-charge` which lets you know how many RUs were consumed by the request.\nThis applies to all item point operations in both the sync and async clients - and can be used by referencing the `get_response_headers()` method of any response as such:\n```python\nfrom azure.cosmos import CosmosClient\nimport os\n\nURL = os.environ['ACCOUNT_URI']\nKEY = os.environ['ACCOUNT_KEY']\nDATABASE_NAME = 'testDatabase'\nCONTAINER_NAME = 'products'\nclient = CosmosClient(URL, credential=KEY)\ndatabase = client.get_database_client(DATABASE_NAME)\ncontainer = database.get_container_client(CONTAINER_NAME)\n\noperation_response = container.create_item({\"id\": \"test_item\", \"productName\": \"test_item\"})\noperation_headers = operation_response.get_response_headers()\netag_value = operation_headers['etag']\nrequest_charge = operation_headers['x-ms-request-charge']\n```\n\n### Using the asynchronous client\n\nThe asynchronous cosmos client is a separate client that looks and works in a similar fashion to the existing synchronous client. However, the async client needs to be imported separately and its methods need to be used with the async/await keywords.\nThe Async client needs to be initialized and closed after usage, which can be done manually or with the use of a context manager. The example below shows how to do so manually. We don't recommend doing it this way, since it requires that you manually call __aenter__() before using the client.\n\n```python\nfrom azure.cosmos.aio import CosmosClient\nimport os\n\nURL = os.environ['ACCOUNT_URI']\nKEY = os.environ['ACCOUNT_KEY']\nDATABASE_NAME = 'testDatabase'\nCONTAINER_NAME = 'products' \n\nasync def create_products():\n client = CosmosClient(URL, credential=KEY)\n await client.__aenter__() # this piece is important for the SDK to cache account information\n database = client.get_database_client(DATABASE_NAME)\n container = database.get_container_client(CONTAINER_NAME)\n for i in range(10):\n await container.upsert_item({\n 'id': 'item{0}'.format(i),\n 'productName': 'Widget',\n 'productModel': 'Model {0}'.format(i)\n }\n )\n await client.close() # the async client must be closed manually if it's not initialized in a with statement\n```\n\nInstead of manually opening and closing the client, it is highly recommended to use the `async with` keywords. This creates a context manager that will initialize and later close the client once you're out of the statement, as well as cache important information the SDK needs. The example below shows how to do so.\n\n```python\nfrom azure.cosmos.aio import CosmosClient\nimport os\n\nURL = os.environ['ACCOUNT_URI']\nKEY = os.environ['ACCOUNT_KEY']\nDATABASE_NAME = 'testDatabase'\nCONTAINER_NAME = 'products'\n\nasync def create_products():\n async with CosmosClient(URL, credential=KEY) as client: # the with statement will automatically initialize and close the async client\n database = client.get_database_client(DATABASE_NAME)\n container = database.get_container_client(CONTAINER_NAME)\n for i in range(10):\n await container.upsert_item({\n 'id': 'item{0}'.format(i),\n 'productName': 'Widget',\n 'productModel': 'Model {0}'.format(i)\n }\n )\n```\n\n### Queries with the asynchronous client\n\nUnlike the synchronous client, the async client does not have an `enable_cross_partition` flag in the request. Queries without a specified partition key value will attempt to do a cross partition query by default. \n\nQuery results can be iterated, but the query's raw output returns an asynchronous iterator. This means that each object from the iterator is an awaitable object, and does not yet contain the true query result. In order to obtain the query results you can use an async for loop, which awaits each result as you iterate on the object, or manually await each query result as you iterate over the asynchronous iterator.\n\nSince the query results are an asynchronous iterator, they can't be cast into lists directly; instead, if you need to create lists from your results, use an async for loop or Python's list comprehension to populate a list:\n\n```python\nfrom azure.cosmos.aio import CosmosClient\nimport os\n\nURL = os.environ['ACCOUNT_URI']\nKEY = os.environ['ACCOUNT_KEY']\nclient = CosmosClient(URL, credential=KEY)\nDATABASE_NAME = 'testDatabase'\ndatabase = client.get_database_client(DATABASE_NAME)\nCONTAINER_NAME = 'products'\ncontainer = database.get_container_client(CONTAINER_NAME)\n\nasync def create_lists():\n results = container.query_items(\n query='SELECT * FROM products p WHERE p.productModel = \"Model 2\"')\n\n # iterates on \"results\" iterator to asynchronously create a complete list of the actual query results\n\n item_list = []\n async for item in results:\n item_list.append(item)\n\n # Asynchronously creates a complete list of the actual query results. This code performs the same action as the for-loop example above.\n item_list = [item async for item in results]\n await client.close()\n```\n\n### Using Integrated Cache\nAn integrated cache is an in-memory cache that helps you ensure manageable costs and low latency as your request volume grows. The integrated cache has two parts: an item cache for point reads and a query cache for queries. The code snippet below shows you how to use this feature with the point read and query cache methods.\n\nThe benefit of using this is that the point reads and queries that hit the integrated cache won't use any RUs. This means you will have a much lower per-operation cost than reads from the backend.\n\n[How to configure the Azure Cosmos DB integrated cache (Preview)][cosmos_configure_integrated_cache]\n\n```python\nimport azure.cosmos.cosmos_client as cosmos_client\nimport os\n\nURL = os.environ['ACCOUNT_URI']\nKEY = os.environ['ACCOUNT_KEY']\nclient = cosmos_client.CosmosClient(URL, credential=KEY)\nDATABASE_NAME = 'testDatabase'\ndatabase = client.get_database_client(DATABASE_NAME)\nCONTAINER_NAME = 'testContainer'\ncontainer = database.get_container_client(CONTAINER_NAME)\n\ndef integrated_cache_snippet():\n item_id = body['id'] \n query = 'SELECT * FROM c'\n\n #item cache\n container.read_item(item=item_id, partition_key=item_id, max_integrated_cache_staleness_in_ms=30000)\n\n #query cache \n container.query_items(query=query,\n partition_key=item_id, max_integrated_cache_staleness_in_ms=30000)\n```\nFor more information on Integrated Cache, see [Azure Cosmos DB integrated cache - Overview][cosmos_integrated_cache].\n\n### Using Transactional Batch\nTransactional batch requests allow you to send several operations to be executed at once within the same partition key.\nIf all operations succeed in the order they're described within the transactional batch operation, the transaction will be committed.\nHowever, if any operation fails, the entire transaction is rolled back.\n\nTransactional batches have a limit of 100 operations per batch, and a total size limit of 1.2Mb for the\nbatch operations being passed in.\n\nTransactional Batch operations look very similar to the singular operations apis, and are tuples containing\n(`operation_type_string`, `args_tuple`, `batch_operation_kwargs_dictionary`), with the kwargs dictionary being optional:\n```python\nbatch_operations = [\n (\"create\", (item_body,), kwargs),\n (\"replace\", (item_id, item_body), kwargs),\n (\"read\", (item_id,), kwargs),\n (\"upsert\", (item_body,), kwargs),\n (\"patch\", (item_id, operations), kwargs),\n (\"delete\", (item_id,), kwargs),\n ]\nbatch_results = container.execute_item_batch(batch_operations=batch_operations, partition_key=partition_key)\n```\nThe batch operation kwargs dictionary is limited, and only takes a total of three different key values.\nIn the case of wanting to use conditional patching within the batch, the use of `filter_predicate` key is available for the\npatch operation, or in case of wanting to use etags with any of the operations, the use of the `if_match_etag`/`if_none_match_etag`\nkeys is available as well.\n```python\nbatch_operations = [\n (\"replace\", (item_id, item_body), {\"if_match_etag\": etag}),\n (\"patch\", (item_id, operations), {\"filter_predicate\": filter_predicate, \"if_none_match_etag\": etag}),\n ]\n```\n\nWe also have some samples showing these transactional batch operations in action with both the [sync][sample_document_mgmt]\nand [async][sample_document_mgmt_async] clients.\n\nIf there is a failure for an operation within the batch, the SDK will raise a `CosmosBatchOperationError` letting you know which operation failed,\nas well as containing the list of failed responses for the failed request.\n\nFor more information on Transactional Batch, see [Azure Cosmos DB Transactional Batch][cosmos_transactional_batch].\n\n### Public Preview - Vector Embeddings and Vector Indexes\nWe have added new capabilities to utilize vector embeddings and vector indexing for users to leverage vector\nsearch utilizing our Cosmos SDK. These two container-level configurations have to be turned on at the account-level\nbefore you can use them.\n\nEach vector embedding should have a path to the relevant vector field in your items being stored, a supported data type\n(float32, int8, uint8), the vector's dimensions, and the distance function being used for that embedding. Vectors indexed \nwith the flat index type can be at most 505 dimensions. Vectors indexed with the quantizedFlat index type can be at most 4,096 dimensions.\nA sample vector embedding policy would look like this:\n```python\nvector_embedding_policy = {\n \"vectorEmbeddings\": [\n {\n \"path\": \"/vector1\",\n \"dataType\": \"float32\",\n \"dimensions\": 256,\n \"distanceFunction\": \"euclidean\"\n },\n {\n \"path\": \"/vector2\",\n \"dataType\": \"int8\",\n \"dimensions\": 200,\n \"distanceFunction\": \"dotproduct\"\n },\n {\n \"path\": \"/vector3\",\n \"dataType\": \"uint8\",\n \"dimensions\": 400,\n \"distanceFunction\": \"cosine\"\n }\n ]\n}\n```\n\nSeparately, vector indexes have been added to the already existing indexing_policy and only require two fields per index:\nthe path to the relevant field to be used, and the type of index from the possible options - flat, quantizedFlat, or diskANN.\nA sample indexing policy with vector indexes would look like this:\n```python\nindexing_policy = {\n \"automatic\": True,\n \"indexingMode\": \"consistent\",\n \"compositeIndexes\": [\n [\n {\"path\": \"/numberField\", \"order\": \"ascending\"},\n {\"path\": \"/stringField\", \"order\": \"descending\"}\n ]\n ],\n \"spatialIndexes\": [\n {\"path\": \"/location/*\", \"types\": [\n \"Point\",\n \"Polygon\"]}\n ],\n \"vectorIndexes\": [\n {\"path\": \"/vector1\", \"type\": \"flat\"},\n {\"path\": \"/vector2\", \"type\": \"quantizedFlat\"},\n {\"path\": \"/vector3\", \"type\": \"diskANN\"}\n ]\n }\n```\n\nFor vector index types of diskANN and quantizedFlat, there are additional options available as well. These are:\n\nquantizationByteSize - the number of bytes used in product quantization of the vectors. A larger value may result in better recall for vector searches at the expense of latency. This applies to index types diskANN and quantizedFlat. The allowed range is between 1 and the minimum between 512 and the vector dimensions. The default value is 64.\n\nindexingSearchListSize - which represents the size of the candidate list of approximate neighbors stored while building the diskANN index as part of the optimization processes. This applies only to index type diskANN. The allowed range is between 25 and 500.\n```python\nindexing_policy = {\n \"automatic\": True,\n \"indexingMode\": \"consistent\",\n \"vectorIndexes\": [\n {\"path\": \"/vector1\", \"type\": \"quantizedFlat\", \"quantizationByteSize\": 8},\n {\"path\": \"/vector2\", \"type\": \"diskANN\", \"indexingSearchListSize\": 50}\n ]\n }\n```\n\nYou would then pass in the relevant policies to your container creation method to ensure these configurations are used by it.\nThe operation will fail if you pass new vector indexes to your indexing policy but forget to pass in an embedding policy.\n```python\ndatabase.create_container(id=container_id, partition_key=PartitionKey(path=\"/id\"),\n indexing_policy=indexing_policy, vector_embedding_policy=vector_embedding_policy)\n```\n***Note: vector embeddings and vector indexes CANNOT be edited by container replace operations. They are only available directly through creation.***\n\n### Public Preview - Vector Search\n\nWith the addition of the vector indexing and vector embedding capabilities, the SDK can now perform order by vector search queries.\nThese queries specify the VectorDistance to use as a metric within the query text. These must always use a TOP or LIMIT clause within the query though,\nsince vector search queries have to look through a lot of data otherwise and may become too expensive or long-running.\nSince these queries are relatively expensive, the SDK sets a default limit of 50000 max items per query - if you'd like to raise that further, you\ncan use the `AZURE_COSMOS_MAX_ITEM_BUFFER_VECTOR_SEARCH` environment variable to do so. However, be advised that queries with too many vector results\nmay have additional latencies associated with searching in the service.\nThe query syntax for these operations looks like this:\n```python\nVectorDistance(, , [,], [,])\n```\nEmbeddings 1 and 2 are the arrays of values for the relevant embeddings, `exact_search` is an optional boolean indicating whether\nto do an exact search vs. an approximate one (default value of false), and `specification` is an optional Json snippet with embedding\nspecs that can include `dataType`, `dimensions` and `distanceFunction`. The specifications within the query will take precedence\nto any configurations previously set by a vector embedding policy.\nA sample vector search query would look something like this:\n```python\n query = \"SELECT TOP 10 c.title,VectorDistance(c.embedding, [{}]) AS \" \\\n \"SimilarityScore FROM c ORDER BY VectorDistance(c.embedding, [{}])\".format(embeddings_string, embeddings_string)\n```\nOr if you'd like to add the optional parameters to the vector distance, you could do this:\n```python\n query = \"SELECT TOP 10 c.title,VectorDistance(c.embedding, [{}], true, {{'dataType': 'float32' , 'distanceFunction': 'cosine'}}) AS \" \\\n \"SimilarityScore FROM c ORDER BY VectorDistance(c.embedding, [{}], true, {{'dataType': \" \\\n \"'float32', 'distanceFunction': 'cosine'}})\".format(embeddings_string, embeddings_string)\n```\nThe `embeddings_string` above would be your string made from your vector embeddings.\nYou can find our sync samples [here][cosmos_index_sample] and our async samples [here][cosmos_index_sample_async] as well to help yourself out.\n\n*Note: For a limited time, if your query operates against a region or emulator that has not yet been updated the client might run into some issues\nnot being able to recognize the new NonStreamingOrderBy capability that makes vector search possible.\nIf this happens, you can set the `AZURE_COSMOS_DISABLE_NON_STREAMING_ORDER_BY` environment variable to `\"True\"` to opt out of this\nfunctionality and continue operating as usual.*\n\n### Public Preview - Full Text Policy and Full Text Indexes\nWe have added new capabilities to utilize full text policies and full text indexing for users to leverage full text search\nutilizing our Cosmos SDK. These two container-level configurations have to be turned on at the account-level\nbefore you can use them.\n\nA full text policy allows the user to define the default language to be used for all full text paths, or to set\na language for each path individually in case the user would like to use full text search on data containing different\nlanguages in different fields.\n\nA sample full text policy would look like this:\n```python\nfull_text_policy = {\n \"defaultLanguage\": \"en-US\",\n \"fullTextPaths\": [\n {\n \"path\": \"/text1\",\n \"language\": \"en-US\"\n },\n {\n \"path\": \"/text2\",\n \"language\": \"en-US\"\n }\n ]\n}\n```\nCurrently, the only supported language is `en-US` - using the relevant ISO-639 language code to ISO-3166 country code.\nAny non-supported language or code will return an exception when trying to use it - which will also include the list of supported languages.\nThis list will include more options in the future; for more information on supported languages, please see [here][cosmos_fts].\n\nFull text search indexes have been added to the already existing indexing_policy and only require the path to the\nrelevant field to be used.\nA sample indexing policy with full text search indexes would look like this:\n```python\nindexing_policy = {\n \"automatic\": True,\n \"indexingMode\": \"consistent\",\n \"compositeIndexes\": [\n [\n {\"path\": \"/numberField\", \"order\": \"ascending\"},\n {\"path\": \"/stringField\", \"order\": \"descending\"}\n ]\n ],\n \"fullTextIndexes\": [\n {\"path\": \"/abstract\"}\n ]\n }\n```\nModifying the index in a container is an asynchronous operation that can take a long time to finish. See [here][cosmos_index_policy_change] for more information.\nFor more information on using full text policies and full text indexes, see [here][cosmos_fts].\n\n### Public Preview - Full Text Search and Hybrid Search\n\nWith the addition of the full text indexing and full text policies, the SDK can now perform full text search and hybrid search queries.\nThese queries can utilize the new query functions `FullTextContains()`, `FullTextContainsAll`, and `FullTextContainsAny` to efficiently\nsearch for the given terms within your item fields.\n\nBeyond these, you can also utilize the new `Order By RANK` and `Order By RANK RRF` along with `FullTextScore` to execute the [BM25][BM25] scoring algorithm\nor [Reciprocal Rank Fusion][RRF] (RRF) on your query, finding the items with the highest relevance to the terms you are looking for.\nAll of these mentioned queries would look something like this:\n\n- `SELECT TOP 10 c.id, c.text FROM c WHERE FullTextContains(c.text, 'quantum')`\n\n\n- `SELECT TOP 10 c.id, c.text FROM c WHERE FullTextContainsAll(c.text, 'quantum', 'theory')`\n\n\n- `SELECT TOP 10 c.id, c.text FROM c WHERE FullTextContainsAny(c.text, 'quantum', 'theory')`\n\n\n- `SELECT TOP 10 c.id, c.text FROM c ORDER BY RANK FullTextScore(c.text, ['quantum', 'theory'])`\n\n\n- `SELECT TOP 10 c.id, c.text FROM c ORDER BY RANK RRF(FullTextScore(c.text, ['quantum', 'theory']), FullTextScore(c.text, ['model']))`\n\n\n- `SELECT TOP 10 c.id, c.text FROM c ORDER BY RANK RRF(FullTextScore(c.text, ['quantum', 'theory']), FullTextScore(c.text, ['model']), VectorDistance(c.embedding, {item_embedding}))\"`\n\nThese queries must always use a TOP or LIMIT clause within the query since hybrid search queries have to look through a lot of data otherwise and may become too expensive or long-running.\nSince these queries are relatively expensive, the SDK sets a default limit of 1000 max items per query - if you'd like to raise that further, you\ncan use the `AZURE_COSMOS_HYBRID_SEARCH_MAX_ITEMS` environment variable to do so. However, be advised that queries with too many vector results\nmay have additional latencies associated with searching in the service.\n\nYou can find our sync samples [here][cosmos_index_sample] and our async samples [here][cosmos_index_sample_async] as well for additional guidance.\n\n## Troubleshooting\n\n### General\n\nWhen you interact with Cosmos DB using the Python SDK, exceptions returned by the service correspond to the same HTTP status codes returned for REST API requests:\n\n[HTTP Status Codes for Azure Cosmos DB][cosmos_http_status_codes]\n\nFor example, if you try to create a container using an ID (name) that's already in use in your Cosmos DB database, a `409` error is returned, indicating the conflict. In the following snippet, the error is handled gracefully by catching the exception and displaying additional information about the error.\n\n```python\ntry:\n database.create_container(id=CONTAINER_NAME, partition_key=PartitionKey(path=\"/productName\"))\nexcept exceptions.CosmosResourceExistsError:\n print(\"\"\"Error creating container\nHTTP status code 409: The ID (name) provided for the container is already in use.\nThe container name must be unique within the database.\"\"\")\n\n```\n### Logging Diagnostics\n\nThis library uses the standard\n[logging](https://docs.python.org/3.5/library/logging.html) library for logging diagnostics.\nBasic information about HTTP sessions (URLs, headers, etc.) is logged at INFO\nlevel.\n\nDetailed DEBUG level logging, including request/response bodies and unredacted\nheaders, can be enabled on a client with the `logging_enable` argument:\n```python\nimport sys\nimport logging\nfrom azure.cosmos import CosmosClient\n\n# Create a logger for the 'azure' SDK\nlogger = logging.getLogger('azure')\nlogger.setLevel(logging.DEBUG)\n\n# Configure a console output\nhandler = logging.StreamHandler(stream=sys.stdout)\nlogger.addHandler(handler)\n\n# This client will log detailed information about its HTTP sessions, at DEBUG level\nclient = CosmosClient(URL, credential=KEY, logging_enable=True)\n```\n\nSimilarly, `logging_enable` can enable detailed logging for a single operation,\neven when it isn't enabled for the client:\n```python\ndatabase = client.create_database(DATABASE_NAME, logging_enable=True)\n```\nAlternatively, you can log using the CosmosHttpLoggingPolicy, which extends from the azure core HttpLoggingPolicy, by passing in your logger to the `logger` argument.\nBy default, it will use the behaviour from HttpLoggingPolicy. Passing in the `enable_diagnostics_logging` argument will enable the\nCosmosHttpLoggingPolicy, and will have additional information in the response relevant to debugging Cosmos issues.\n```python\nimport logging\nfrom azure.cosmos import CosmosClient\n\n#Create a logger for the 'azure' SDK\nlogger = logging.getLogger('azure')\nlogger.setLevel(logging.DEBUG)\n\n# Configure a file output\nhandler = logging.FileHandler(filename=\"azure\")\nlogger.addHandler(handler)\n\n# This client will log diagnostic information from the HTTP session by using the CosmosHttpLoggingPolicy.\n# Since we passed in the logger to the client, it will log information on every request.\nclient = CosmosClient(URL, credential=KEY, logger=logger, enable_diagnostics_logging=True)\n```\nSimilarly, logging can be enabled for a single operation by passing in a logger to the singular request.\nHowever, if you desire to use the CosmosHttpLoggingPolicy to obtain additional information, the `enable_diagnostics_logging` argument needs to be passed in at the client constructor.\n```python\n# This example enables the CosmosHttpLoggingPolicy and uses it with the `logger` passed in to the `create_database` request.\nclient = CosmosClient(URL, credential=KEY, enable_diagnostics_logging=True)\ndatabase = client.create_database(DATABASE_NAME, logger=logger)\n```\n\n### Telemetry\nAzure Core provides the ability for our Python SDKs to use OpenTelemetry with them. The only packages that need to be installed\nto use this functionality are the following:\n```bash\npip install azure-core-tracing-opentelemetry\npip install opentelemetry-sdk\n```\nFor more information on this, we recommend taking a look at this [document](https://github.com/Azure/azure-sdk-for-python/blob/main/sdk/core/azure-core-tracing-opentelemetry/README.md) \nfrom Azure Core describing how to set it up. We have also added a [sample file][telemetry_sample] to show how it can\nbe used with our SDK. This works the same way regardless of the Cosmos client you are using.\n\n## Next steps\n\nFor more extensive documentation on the Cosmos DB service, see the [Azure Cosmos DB documentation][cosmos_docs] on docs.microsoft.com.\n\n\n[azure_cli]: https://docs.microsoft.com/cli/azure\n[azure_portal]: https://portal.azure.com\n[azure_sub]: https://azure.microsoft.com/free/\n[cloud_shell]: https://docs.microsoft.com/azure/cloud-shell/overview\n[cosmos_account_create]: https://docs.microsoft.com/azure/cosmos-db/how-to-manage-database-account\n[cosmos_account]: https://docs.microsoft.com/azure/cosmos-db/account-overview\n[cosmos_container]: https://docs.microsoft.com/azure/cosmos-db/databases-containers-items#azure-cosmos-containers\n[cosmos_database]: https://docs.microsoft.com/azure/cosmos-db/databases-containers-items#azure-cosmos-databases\n[cosmos_docs]: https://docs.microsoft.com/azure/cosmos-db/\n[cosmos_samples]: https://github.com/Azure/azure-sdk-for-python/tree/main/sdk/cosmos/azure-cosmos/samples\n[cosmos_pypi]: https://pypi.org/project/azure-cosmos/\n[cosmos_http_status_codes]: https://docs.microsoft.com/rest/api/cosmos-db/http-status-codes-for-cosmosdb\n[cosmos_item]: https://docs.microsoft.com/azure/cosmos-db/databases-containers-items#azure-cosmos-items\n[cosmos_models]: https://github.com/Azure/azure-sdk-for-python/tree/main/sdk/cosmos/azure-cosmos/azure/cosmos/_models.py\n[cosmos_request_units]: https://docs.microsoft.com/azure/cosmos-db/request-units\n[cosmos_resources]: https://docs.microsoft.com/azure/cosmos-db/databases-containers-items\n[cosmos_sql_queries]: https://docs.microsoft.com/azure/cosmos-db/how-to-sql-query\n[cosmos_ttl]: https://docs.microsoft.com/azure/cosmos-db/time-to-live\n[cosmos_integrated_cache]: https://docs.microsoft.com/azure/cosmos-db/integrated-cache\n[cosmos_configure_integrated_cache]: https://docs.microsoft.com/azure/cosmos-db/how-to-configure-integrated-cache\n[python]: https://www.python.org/downloads/\n[ref_container_delete_item]: https://aka.ms/azsdk-python-cosmos-ref-delete-item\n[ref_container_query_items]: https://aka.ms/azsdk-python-cosmos-ref-query-items\n[ref_container_upsert_item]: https://aka.ms/azsdk-python-cosmos-ref-upsert-item\n[ref_container]: https://aka.ms/azsdk-python-cosmos-ref-container\n[ref_cosmos_sdk]: https://aka.ms/azsdk-python-cosmos-ref\n[ref_cosmosclient_create_database]: https://aka.ms/azsdk-python-cosmos-ref-create-database\n[ref_cosmosclient]: https://aka.ms/azsdk-python-cosmos-ref-cosmos-client\n[ref_database]: https://aka.ms/azsdk-python-cosmos-ref-database\n[ref_httpfailure]: https://aka.ms/azsdk-python-cosmos-ref-http-failure\n[sample_database_mgmt]: https://github.com/Azure/azure-sdk-for-python/tree/main/sdk/cosmos/azure-cosmos/samples/database_management.py\n[sample_document_mgmt]: https://github.com/Azure/azure-sdk-for-python/tree/main/sdk/cosmos/azure-cosmos/samples/document_management.py\n[sample_document_mgmt_async]: https://github.com/Azure/azure-sdk-for-python/tree/main/sdk/cosmos/azure-cosmos/samples/document_management_async.py\n[sample_examples_misc]: https://github.com/Azure/azure-sdk-for-python/tree/main/sdk/cosmos/azure-cosmos/samples/examples.py\n[source_code]: https://github.com/Azure/azure-sdk-for-python/tree/main/sdk/cosmos/azure-cosmos\n[venv]: https://docs.python.org/3/library/venv.html\n[virtualenv]: https://virtualenv.pypa.io\n[telemetry_sample]: https://github.com/Azure/azure-sdk-for-python/tree/main/sdk/cosmos/azure-cosmos/samples/tracing_open_telemetry.py\n[timeouts_document]: https://github.com/Azure/azure-sdk-for-python/tree/main/sdk/cosmos/azure-cosmos/docs/TimeoutAndRetriesConfig.md\n[cosmos_transactional_batch]: https://learn.microsoft.com/azure/cosmos-db/nosql/transactional-batch\n[cosmos_concurrency_sample]: https://github.com/Azure/azure-sdk-for-python/tree/main/sdk/cosmos/azure-cosmos/samples/concurrency_sample.py\n[cosmos_index_sample]: https://github.com/Azure/azure-sdk-for-python/tree/main/sdk/cosmos/azure-cosmos/samples/index_management.py\n[cosmos_index_sample_async]: https://github.com/Azure/azure-sdk-for-python/tree/main/sdk/cosmos/azure-cosmos/samples/index_management_async.py\n[RRF]: https://learn.microsoft.com/azure/search/hybrid-search-ranking\n[BM25]: https://learn.microsoft.com/azure/search/index-similarity-and-scoring\n[cosmos_fts]: https://aka.ms/cosmosfulltextsearch\n[cosmos_index_policy_change]: https://learn.microsoft.com/azure/cosmos-db/index-policy#modifying-the-indexing-policy\n\n## Contributing\n\nThis project welcomes contributions and suggestions. Most contributions require you to agree to a\nContributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us\nthe rights to use your contribution. For details, visit https://cla.microsoft.com.\n\nWhen you submit a pull request, a CLA-bot will automatically determine whether you need to provide\na CLA and decorate the PR appropriately (e.g., label, comment). Simply follow the instructions\nprovided by the bot. You will only need to do this once across all repos using our CLA.\n\nThis project has adopted the [Microsoft Open Source Code of Conduct](https://opensource.microsoft.com/codeofconduct/).\nFor more information see the [Code of Conduct FAQ](https://opensource.microsoft.com/codeofconduct/faq/) or\ncontact [opencode@microsoft.com](mailto:opencode@microsoft.com) with any additional questions or comments.\n\n## Release History\n\n### 4.9.0 (2024-11-18)\n\n#### Features Added\n* Added full text policy and full text indexing policy. See [PR 37891](https://github.com/Azure/azure-sdk-for-python/pull/37891).\n* Added support for full text search and hybrid search queries. See [PR 38275](https://github.com/Azure/azure-sdk-for-python/pull/38275).\n\n### 4.8.0 (2024-11-12)\nThis version and all future versions will support Python 3.13.\n\n#### Features Added\n* Added response headers directly to SDK item point operation responses. See [PR 35791](https://github.com/Azure/azure-sdk-for-python/pull/35791).\n* SDK will now retry all ServiceRequestErrors (failing outgoing requests) before failing. Default number of retries is 3. See [PR 36514](https://github.com/Azure/azure-sdk-for-python/pull/36514).\n* Added Retry Policy for Container Recreate in the Python SDK. See [PR 36043](https://github.com/Azure/azure-sdk-for-python/pull/36043).\n* Added option to disable write payload on writes. See [PR 37365](https://github.com/Azure/azure-sdk-for-python/pull/37365).\n* Added get feed ranges API. See [PR 37687](https://github.com/Azure/azure-sdk-for-python/pull/37687).\n* Added feed range support in `query_items_change_feed`. See [PR 37687](https://github.com/Azure/azure-sdk-for-python/pull/37687).\n* Added **provisional** helper APIs for managing session tokens. See [PR 36971](https://github.com/Azure/azure-sdk-for-python/pull/36971).\n* Added ability to get feed range for a partition key. See [PR 36971](https://github.com/Azure/azure-sdk-for-python/pull/36971).\n\n#### Breaking Changes\n* Item-level point operations will now return `CosmosDict` and `CosmosList` response types. \nResponses will still be able to be used directly as previously, but will now have access to their response headers without need for a response hook. See [PR 35791](https://github.com/Azure/azure-sdk-for-python/pull/35791).\nFor more information on this, see our README section [here](https://github.com/Azure/azure-sdk-for-python/blob/main/sdk/cosmos/azure-cosmos/README.md#using-item-operation-response-headers).\n\n#### Bugs Fixed\n* Consolidated Container Properties Cache to be in the Client to cache partition key definition and container rid to avoid unnecessary container reads. See [PR 35731](https://github.com/Azure/azure-sdk-for-python/pull/35731).\n* Fixed bug with client hangs when running into WriteForbidden exceptions. See [PR 36514](https://github.com/Azure/azure-sdk-for-python/pull/36514).\n* Added retry handling logic for DatabaseAccountNotFound exceptions. See [PR 36514](https://github.com/Azure/azure-sdk-for-python/pull/36514).\n* Fixed SDK regex validation that would not allow for item ids to be longer than 255 characters. See [PR 36569](https://github.com/Azure/azure-sdk-for-python/pull/36569).\n* Fixed issue where 'NoneType' object has no attribute error was raised when a session retry happened during a query. See [PR 37578](https://github.com/Azure/azure-sdk-for-python/pull/37578).\n* Fixed issue where passing subpartition partition key values as a tuple in a query would raise an error. See [PR 38136](https://github.com/Azure/azure-sdk-for-python/pull/38136).\n* Batch requests will now be properly considered as Write operation. See [PR 38365](https://github.com/Azure/azure-sdk-for-python/pull/38365).\n\n#### Other Changes\n* Getting offer thoughput when it has not been defined in a container will now give a 404/10004 instead of just a 404. See [PR 36043](https://github.com/Azure/azure-sdk-for-python/pull/36043).\n* Incomplete Partition Key Extractions in documents for Subpartitioning now gives 400/1001 instead of just a 400. See [PR 36043](https://github.com/Azure/azure-sdk-for-python/pull/36043).\n* SDK will now make database account calls every 5 minutes to refresh location cache. See [PR 36514](https://github.com/Azure/azure-sdk-for-python/pull/36514).\n\n### 4.7.0 (2024-05-15)\n\n#### Features Added\n* Adds vector embedding policy and vector indexing policy. See [PR 34882](https://github.com/Azure/azure-sdk-for-python/pull/34882).\n* Adds support for vector search non-streaming order by queries. See [PR 35468](https://github.com/Azure/azure-sdk-for-python/pull/35468).\n* Adds support for using the start time option for change feed query API. See [PR 35090](https://github.com/Azure/azure-sdk-for-python/pull/35090).\n\n#### Bugs Fixed\n* Fixed a bug where change feed query in Async client was not returning all pages due to case-sensitive response headers. See [PR 35090](https://github.com/Azure/azure-sdk-for-python/pull/35090).\n* Fixed a bug when a retryable exception occurs in the first page of a query execution causing query to return 0 results. See [PR 35090](https://github.com/Azure/azure-sdk-for-python/pull/35090).\n\n### 4.6.1 (2024-05-15)\n\n### 4.6.0 (2024-03-14)\n\n#### Features Added\n* GA release of hierarchical partitioning, index metrics and transactional batch.\n\n#### Bugs Fixed\n* Keyword arguments were not being passed down for `create_container_if_not_exists()` methods. See [PR 34286](https://github.com/Azure/azure-sdk-for-python/pull/34286).\n\n#### Other Changes\n* Made several updates to the type hints used throughout the SDK for greater detail. See [PR 33269](https://github.com/Azure/azure-sdk-for-python/pull/33269), [PR 33341](https://github.com/Azure/azure-sdk-for-python/pull/33341), [PR 33738](https://github.com/Azure/azure-sdk-for-python/pull/33738).\n\n### 4.5.2b5 (2024-03-02)\n\n#### Bugs Fixed\n* Fixed bug with async lock not properly releasing on async global endpoint manager. see [PR 34579](https://github.com/Azure/azure-sdk-for-python/pull/34579).\n\n#### Other Changes\n* Marked `computed_properties` keyword as provisional, un-marked `continuation_token_limit` as provisional. See [PR 34207](https://github.com/Azure/azure-sdk-for-python/pull/34207).\n\n### 4.5.2b4 (2024-02-02)\nThis version and all future versions will require Python 3.8+.\n\n#### Features Added\n* Added **preview** support for Computed Properties on Python SDK (Must be enabled on the account level before it can be used). See [PR 33626](https://github.com/Azure/azure-sdk-for-python/pull/33626).\n\n#### Bugs Fixed\n* Made use of `response_hook` thread-safe in the sync client. See [PR 33790](https://github.com/Azure/azure-sdk-for-python/pull/33790).\n* Fixed bug with the session container not being properly maintained. See [33738](https://github.com/Azure/azure-sdk-for-python/pull/33738).\n\n### 4.5.2b3 (2023-11-10)\n\n#### Features Added\n* Added support for capturing Index Metrics in query operations. See [PR 33034](https://github.com/Azure/azure-sdk-for-python/pull/33034).\n\n### 4.5.2b2 (2023-10-31)\n\n#### Features Added\n* Added support for Transactional Batch. See [PR 32508](https://github.com/Azure/azure-sdk-for-python/pull/32508).\n* Added **preview** support for Priority Based Throttling/Priority Based Execution (Must be enabled at the account level before it can be used). See [PR 32441](https://github.com/Azure/azure-sdk-for-python/pull/32441/).\n\n### 4.5.2b1 (2023-10-17)\n\n#### Features Added\n* Added support for Hierarchical Partitioning, also known as Subpartitioning. See [PR 31121](https://github.com/Azure/azure-sdk-for-python/pull/31121).\n\n#### Bugs Fixed\n* Small fix to the `offer_throughput` option in the async client's `create_database_if_not_exists` method, which was previously misspelled as `offerThroughput`.\nSee [PR 32076](https://github.com/Azure/azure-sdk-for-python/pull/32076).\n\n#### Other Changes\n* Marked the outdated `diagnostics.py` file for deprecation since we now recommend the use of our `CosmosHttpLoggingPolicy` for diagnostics.\nFor more on the `CosmosHttpLoggingPolicy` see our [README](https://github.com/Azure/azure-sdk-for-python/tree/main/sdk/cosmos/azure-cosmos#logging-diagnostics).\n\n### 4.5.1 (2023-09-12)\n\n#### Bugs Fixed\n* Fixed bug when query with DISTINCT + OFFSET/LIMIT operators returns unexpected result. See [PR 31925](https://github.com/Azure/azure-sdk-for-python/pull/31925).\n\n#### Other Changes\n* Added additional checks for resource creation using specific characters that cause issues. See [PR 31861](https://github.com/Azure/azure-sdk-for-python/pull/31861).\n\n### 4.5.0 (2023-08-09)\n\n#### Features Added\n* Added support for continuation tokens for streamable cross partition queries. See [PR 31189](https://github.com/Azure/azure-sdk-for-python/pull/31189).\n\n#### Bugs Fixed\n* Fixed bug with async `create_database_if_not_exists` method not working when passing `offer_throughput` as an option. See [PR 31478](https://github.com/Azure/azure-sdk-for-python/pull/31478).\n\n#### Other Changes\n* Renamed `response_continuation_token_limit_in_kb` to `continuation_token_limit` for GA. See [PR 31532](https://github.com/Azure/azure-sdk-for-python/pull/31532).\n\n### 4.4.1b1 (2023-07-25)\n\n#### Features Added\n* Added ability to limit continuation token size when querying for items. See [PR 30731](https://github.com/Azure/azure-sdk-for-python/pull/30731)\n\n#### Bugs Fixed\n* Fixed bug with async patch_item method. See [PR 30804](https://github.com/Azure/azure-sdk-for-python/pull/30804).\n\n### 4.4.0 (2023-06-09)\n\n#### Features Added\n- GA release of Patch API and Delete All Items By Partition Key\n\n### 4.4.0b2 (2023-05-22)\n\n#### Features Added\n* Added conditional patching for Patch operations. See [PR 30455](https://github.com/Azure/azure-sdk-for-python/pull/30455).\n\n#### Bugs Fixed\n* Fixed bug with non english locales causing an error with the RFC 1123 Date Format. See [PR 30125](https://github.com/Azure/azure-sdk-for-python/pull/30125).\n\n#### Other Changes\n* Refactoring of our client `connection_timeout` and `request_timeout` configurations. See [PR 30171](https://github.com/Azure/azure-sdk-for-python/pull/30171).\n\n### 4.4.0b1 (2023-04-11)\n\n#### Features Added\n - Added **preview** delete all items by partition key functionality. See [PR 29186](https://github.com/Azure/azure-sdk-for-python/pull/29186). For more information on Partition Key Delete, please see [Azure Cosmos DB Partition Key Delete](https://learn.microsoft.com/azure/cosmos-db/nosql/how-to-delete-by-partition-key?tabs=python-example).\n - Added **preview** partial document update (Patch API) functionality and container methods for patching items with operations. See [PR 29497](https://github.com/Azure/azure-sdk-for-python/pull/29497). For more information on Patch, please see [Azure Cosmos DB Partial Document Update](https://learn.microsoft.com/azure/cosmos-db/partial-document-update).\n\n#### Bugs Fixed\n* Fixed bug in method `create_container_if_not_exists()` of async database client for unexpected kwargs being passed into `read()` method used internally. See [PR 29136](https://github.com/Azure/azure-sdk-for-python/pull/29136).\n* Fixed bug with method `query_items()` of our async container class, where partition key and cross partition headers would both be set when using partition keys. See [PR 29366](https://github.com/Azure/azure-sdk-for-python/pull/29366/).\n* Fixed bug with client not properly surfacing errors for invalid credentials and identities with insufficient permissions. Users running into 'NoneType has no attribute ConsistencyPolicy' errors when initializing their clients will now see proper authentication exceptions. See [PR 29256](https://github.com/Azure/azure-sdk-for-python/pull/29256).\n\n#### Other Changes\n* Removed use of `six` package within the SDK.\n\n### 4.3.1 (2023-02-23)\n\n#### Features Added\n - Added `correlated_activity_id` for query operations.\n - Added cross regional retries for Service Unavailable/Request Timeouts for read/Query Plan operations.\n - GA release of CosmosHttpLoggingPolicy and autoscale feature.\n\n#### Bugs Fixed\n- Bug fix to address queries with VALUE MAX (or any other aggregate) that run into an issue if the query is executed on a container with at least one \"empty\" partition.\n\n### 4.3.1b1 (2022-09-19)\n\n#### Features Added\n- GA release of integrated cache functionality. For more information on integrated cache please see [Azure Cosmos DB integrated cache](https://docs.microsoft.com/azure/cosmos-db/integrated-cache).\n- Added ability to replace analytical ttl on containers. For more information on analytical ttl please see [Azure Cosmos DB analytical store](https://docs.microsoft.com/azure/cosmos-db/analytical-store-introduction).\n- Added `CosmosHttpLoggingPolicy` to replace `HttpLoggingPolicy` for logging HTTP sessions.\n- Added the ability to create containers and databases with autoscale properties for the sync and async clients.\n- Added the ability to update autoscale throughput properties.\n\n#### Bugs Fixed\n- Fixed parsing of args for overloaded `container.read()` method.\n- Fixed `validate_cache_staleness_value()` method to allow max_integrated_cache_staleness to be an integer greater than or equal to 0.\n- Fixed `__aiter__()` method by removing the async keyword.\n\n### 4.3.0 (2022-05-23)\n#### Features Added\n- GA release of Async I/O APIs, including all changes from 4.3.0b1 to 4.3.0b4.\n\n#### Breaking Changes\n- Method signatures have been updated to use keyword arguments instead of positional arguments for most method options in the async client.\n- Bugfix: Automatic Id generation for items was turned on for `upsert_items()` method when no 'id' value was present in document body.\nMethod call will now require an 'id' field to be present in the document body.\n\n#### Other Changes\n- Deprecated offer-named methods in favor of their new throughput-named counterparts (`read_offer` -> `get_throughput`).\n- Marked the GetAuthorizationHeader method for deprecation since it will no longer be public in a future release.\n- Added samples showing how to configure retry options for both the sync and async clients.\n- Deprecated the `connection_retry_policy` and `retry_options` options in the sync client.\n- Added user warning to non-query methods trying to use `populate_query_metrics` options.\n\n### 4.3.0b4 (2022-04-07)\n\n#### Features Added\n- Added support for AAD authentication for the async client.\n- Added support for AAD authentication for the sync client.\n\n#### Other Changes\n- Changed `_set_partition_key` return typehint in async client.\n\n### 4.3.0b3 (2022-03-10)\n\n>[WARNING]\n>The default `Session` consistency bugfix will impact customers whose database accounts have a `Bounded Staleness` or `Strong`\n> consistency level, and were previously not sending `Session` as a consistency_level parameter when initializing\n> their clients.\n> Default consistency level for the sync and async clients is no longer \"Session\" and will instead be set to the \n consistency level of the user's cosmos account setting on initialization if not passed during client initialization. \n> Please see [Consistency Levels in Azure Cosmos DB](https://docs.microsoft.com/azure/cosmos-db/consistency-levels) \n> for more details on consistency levels, or the README section on this change [here](https://github.com/Azure/azure-sdk-for-python/tree/main/sdk/cosmos/azure-cosmos#note-on-client-consistency-levels).\n\n#### Features Added\n- Added new **provisional** `max_integrated_cache_staleness_in_ms` parameter to read item and query items APIs in order\n to make use of the **preview** CosmosDB integrated cache functionality [See PR #22946](https://github.com/Azure/azure-sdk-for-python/pull/22946).\n Please see [Azure Cosmos DB integrated cache](https://docs.microsoft.com/azure/cosmos-db/integrated-cache) for more details.\n- Added support for split-proof queries for the async client.\n\n### Bugs fixed\n- Default consistency level for the sync and async clients is no longer `Session` and will instead be set to the \n consistency level of the user's cosmos account setting on initialization if not passed during client initialization. \n This change will impact client application in terms of RUs and latency. Users relying on default `Session` consistency\n will need to pass it explicitly if their account consistency is different than `Session`.\n Please see [Consistency Levels in Azure Cosmos DB](https://docs.microsoft.com/azure/cosmos-db/consistency-levels) for more details. \n- Fixed invalid request body being sent when passing in `serverScript` body parameter to replace operations for trigger, sproc and udf resources.\n- Moved `is_system_key` logic in async client.\n- Fixed TypeErrors not being thrown when passing in invalid connection retry policies to the client.\n\n### 4.3.0b2 (2022-01-25)\n\nThis version and all future versions will require Python 3.6+. Python 2.7 is no longer supported.\nWe will also be removing support for Python 3.6 and will only support Python 3.7+ starting December 2022.\n\n#### Features Added\n- Added support for split-proof queries for the sync client.\n\n#### Other Changes\n- Added async user agent for async client.\n\n### 4.3.0b1 (2021-12-14)\n\n#### Features Added\n- Added language native async i/o client.\n\n### 4.2.0 (2020-10-08)\n\n**Bug fixes**\n- Fixed bug where continuation token is not honored when query_iterable is used to get results by page. Issue #13265.\n- Fixed bug where resource tokens not being honored for document reads and deletes. Issue #13634.\n\n**New features**\n- Added support for passing partitionKey while querying changefeed. Issue #11689.\n\n### 4.1.0 (2020-08-10)\n\n- Added deprecation warning for \"lazy\" indexing mode. The backend no longer allows creating containers with this mode and will set them to consistent instead.\n\n**New features**\n- Added the ability to set the analytical storage TTL when creating a new container.\n\n**Bug fixes**\n- Fixed support for dicts as inputs for get_client APIs.\n- Fixed Python 2/3 compatibility in query iterators.\n- Fixed type hint error. Issue #12570 - thanks @sl-sandy.\n- Fixed bug where options headers were not added to upsert_item function. Issue #11791 - thank you @aalapatirvbd.\n- Fixed error raised when a non string ID is used in an item. It now raises TypeError rather than AttributeError. Issue #11793 - thank you @Rabbit994.\n\n\n### 4.0.0 (2020-05-20)\n\n- Stable release.\n- Added HttpLoggingPolicy to pipeline to enable passing in a custom logger for request and response headers.\n\n\n## 4.0.0b6\n\n- Fixed bug in synchronized_request for media APIs.\n- Removed MediaReadMode and MediaRequestTimeout from ConnectionPolicy as media requests are not supported.\n\n\n## 4.0.0b5\n\n- azure.cosmos.errors module deprecated and replaced by azure.cosmos.exceptions\n- The access condition parameters (`access_condition`, `if_match`, `if_none_match`) have been deprecated in favor of separate `match_condition` and `etag` parameters.\n- Fixed bug in routing map provider.\n- Added query Distinct, Offset and Limit support.\n- Default document query execution context now used for\n - ChangeFeed queries\n - single partition queries (partitionkey, partitionKeyRangeId is present in options)\n - Non document queries\n- Errors out for aggregates on multiple partitions, with enable cross partition query set to true, but no \"value\" keyword present\n- Hits query plan endpoint for other scenarios to fetch query plan\n- Added `__repr__` support for Cosmos entity objects.\n- Updated documentation.\n\n\n## 4.0.0b4\n\n- Added support for a `timeout` keyword argument to all operations to specify an absolute timeout in seconds\n within which the operation must be completed. If the timeout value is exceeded, a `azure.cosmos.errors.CosmosClientTimeoutError` will be raised.\n- Added a new `ConnectionRetryPolicy` to manage retry behaviour during HTTP connection errors.\n- Added new constructor and per-operation configuration keyword arguments:\n - `retry_total` - Maximum retry attempts.\n - `retry_backoff_max` - Maximum retry wait time in seconds.\n - `retry_fixed_interval` - Fixed retry interval in milliseconds.\n - `retry_read` - Maximum number of socket read retry attempts.\n - `retry_connect` - Maximum number of connection error retry attempts.\n - `retry_status` - Maximum number of retry attempts on error status codes.\n - `retry_on_status_codes` - A list of specific status codes to retry on.\n - `retry_backoff_factor` - Factor to calculate wait time between retry attempts.\n\n## 4.0.0b3\n\n- Added `create_database_if_not_exists()` and `create_container_if_not_exists` functionalities to CosmosClient and Database respectively.\n\n## 4.0.0b2\n\nVersion 4.0.0b2 is the second iteration in our efforts to build a more Pythonic client library.\n\n**Breaking changes**\n\n- The client connection has been adapted to consume the HTTP pipeline defined in `azure.core.pipeline`.\n- Interactive objects have now been renamed as proxies. This includes:\n - `Database` -> `DatabaseProxy`\n - `User` -> `UserProxy`\n - `Container` -> `ContainerProxy`\n - `Scripts` -> `ScriptsProxy`\n- The constructor of `CosmosClient` has been updated:\n - The `auth` parameter has been renamed to `credential` and will now take an authentication type directly. This means the master key value, a dictionary of resource tokens, or a list of permissions can be passed in. However the old dictionary format is still supported.\n - The `connection_policy` parameter has been made a keyword only parameter, and while it is still supported, each of the individual attributes of the policy can now be passed in as explicit keyword arguments:\n - `request_timeout`\n - `media_request_timeout`\n - `connection_mode`\n - `media_read_mode`\n - `proxy_config`\n - `enable_endpoint_discovery`\n - `preferred_locations`\n - `multiple_write_locations`\n- A new classmethod constructor has been added to `CosmosClient` to enable creation via a connection string retrieved from the Azure portal.\n- Some `read_all` operations have been renamed to `list` operations:\n - `CosmosClient.read_all_databases` -> `CosmosClient.list_databases`\n - `Container.read_all_conflicts` -> `ContainerProxy.list_conflicts`\n - `Database.read_all_containers` -> `DatabaseProxy.list_containers`\n - `Database.read_all_users` -> `DatabaseProxy.list_users`\n - `User.read_all_permissions` -> `UserProxy.list_permissions`\n- All operations that take `request_options` or `feed_options` parameters, these have been moved to keyword only parameters. In addition, while these options dictionaries are still supported, each of the individual options within the dictionary are now supported as explicit keyword arguments.\n- The error hierarchy is now inherited from `azure.core.AzureError` instead of `CosmosError` which has been removed.\n - `HTTPFailure` has been renamed to `CosmosHttpResponseError`\n - `JSONParseFailure` has been removed and replaced by `azure.core.DecodeError`\n - Added additional errors for specific response codes:\n - `CosmosResourceNotFoundError` for status 404\n - `CosmosResourceExistsError` for status 409\n - `CosmosAccessConditionFailedError` for status 412\n- `CosmosClient` can now be run in a context manager to handle closing the client connection.\n- Iterable responses (e.g. query responses and list responses) are now of type `azure.core.paging.ItemPaged`. The method `fetch_next_block` has been replaced by a secondary iterator, accessed by the `by_page` method.\n\n## 4.0.0b1\n\nVersion 4.0.0b1 is the first preview of our efforts to create a user-friendly and Pythonic client library for Azure Cosmos. For more information about this, and preview releases of other Azure SDK libraries, please visit https://aka.ms/azure-sdk-preview1-python.\n\n**Breaking changes: New API design**\n\n- Operations are now scoped to a particular client:\n - `CosmosClient`: This client handles account-level operations. This includes managing service properties and listing the databases within an account.\n - `Database`: This client handles database-level operations. This includes creating and deleting containers, users and stored procedures. It can be accessed from a `CosmosClient` instance by name.\n - `Container`: This client handles operations for a particular container. This includes querying and inserting items and managing properties.\n - `User`: This client handles operations for a particular user. This includes adding and deleting permissions and managing user properties.\n \n These clients can be accessed by navigating down the client hierarchy using the `get__client` method. For full details on the new API, please see the [reference documentation](https://aka.ms/azsdk-python-cosmos-ref).\n- Clients are accessed by name rather than by Id. No need to concatenate strings to create links.\n- No more need to import types and methods from individual modules. The public API surface area is available directly in the `azure.cosmos` package.\n- Individual request properties can be provided as keyword arguments rather than constructing a separate `RequestOptions` instance.\n\n## 3.0.2\n\n- Added Support for MultiPolygon Datatype\n- Bug Fix in Session Read Retry Policy\n- Bug Fix for Incorrect padding issues while decoding base 64 strings\n\n## 3.0.1\n\n- Bug fix in LocationCache\n- Bug fix endpoint retry logic\n- Fixed documentation\n\n## 3.0.0\n\n- Multi-region write support added\n- Naming changes\n - DocumentClient to CosmosClient\n - Collection to Container\n - Document to Item\n - Package name updated to \"azure-cosmos\"\n - Namespace updated to \"azure.cosmos\"\n\n## 2.3.3\n\n- Added support for proxy\n- Added support for reading change feed\n- Added support for collection quota headers\n- Bugfix for large session tokens issue\n- Bugfix for ReadMedia API\n- Bugfix in partition key range cache\n\n## 2.3.2\n\n- Added support for default retries on connection issues.\n\n## 2.3.1\n\n- Updated documentation to reference Azure Cosmos DB instead of Azure DocumentDB.\n\n## 2.3.0\n\n- This SDK version requires the latest version of Azure Cosmos DB Emulator available for download from https://aka.ms/cosmosdb-emulator.\n\n## 2.2.1\n\n- bugfix for aggregate dict\n- bugfix for trimming slashes in the resource link\n- tests for unicode encoding\n\n## 2.2.0\n\n- Added support for Request Unit per Minute (RU/m) feature.\n- Added support for a new consistency level called ConsistentPrefix.\n\n## 2.1.0\n\n- Added support for aggregation queries (COUNT, MIN, MAX, SUM, and AVG).\n- Added an option for disabling SSL verification when running against DocumentDB Emulator.\n- Removed the restriction of dependent requests module to be exactly 2.10.0.\n- Lowered minimum throughput on partitioned collections from 10,100 RU/s to 2500 RU/s.\n- Added support for enabling script logging during stored procedure execution.\n- REST API version bumped to '2017-01-19' with this release.\n\n## 2.0.1\n\n- Made editorial changes to documentation comments.\n\n## 2.0.0\n\n- Added support for Python 3.5.\n- Added support for connection pooling using the requests module.\n- Added support for session consistency.\n- Added support for TOP/ORDERBY queries for partitioned collections.\n\n## 1.9.0\n\n- Added retry policy support for throttled requests. (Throttled requests receive a request rate too large exception, error code 429.)\n By default, DocumentDB retries nine times for each request when error code 429 is encountered, honoring the retryAfter time in the response header.\n A fixed retry interval time can now be set as part of the RetryOptions property on the ConnectionPolicy object if you want to ignore the retryAfter time returned by server between the retries.\n DocumentDB now waits for a maximum of 30 seconds for each request that is being throttled (irrespective of retry count) and returns the response with error code 429.\n This time can also be overridden in the RetryOptions property on ConnectionPolicy object.\n\n- DocumentDB now returns x-ms-throttle-retry-count and x-ms-throttle-retry-wait-time-ms as the response headers in every request to denote the throttle retry count\n and the cumulative time the request waited between the retries.\n\n- Removed the RetryPolicy class and the corresponding property (retry_policy) exposed on the document_client class and instead introduced a RetryOptions class\n exposing the RetryOptions property on ConnectionPolicy class that can be used to override some of the default retry options.\n\n## 1.8.0\n\n- Added the support for geo-replicated database accounts.\n- Test fixes to move the global host and masterKey into the individual test classes.\n\n## 1.7.0\n\n- Added the support for Time To Live(TTL) feature for documents.\n\n## 1.6.1\n\n- Bug fixes related to server side partitioning to allow special characters in partitionkey path.\n\n## 1.6.0\n\n- Added the support for server side partitioned collections feature.\n\n## 1.5.0\n\n- Added Client-side sharding framework to the SDK. Implemented HashPartionResolver and RangePartitionResolver classes.\n\n## 1.4.2\n\n- Implement Upsert. New UpsertXXX methods added to support Upsert feature.\n- Implement ID Based Routing. No public API changes, all changes internal.\n\n## 1.3.0\n\n- Release skipped to bring version number in alignment with other SDKs\n\n## 1.2.0\n\n- Supports GeoSpatial index.\n- Validates id property for all resources. Ids for resources cannot contain ?, /, #, \\\\, characters or end with a space.\n- Adds new header \"index transformation progress\" to ResourceResponse.\n\n## 1.1.0\n\n- Implements V2 indexing policy\n\n## 1.0.1\n\n- Supports proxy connection\n\n","description_content_type":"text/markdown","docs_url":null,"download_url":null,"downloads":{"last_day":-1,"last_month":-1,"last_week":-1},"dynamic":null,"home_page":"https://github.com/Azure/azure-sdk-for-python","keywords":"azure, azure sdk","license":"MIT License","license_expression":null,"license_files":null,"maintainer":"Microsoft","maintainer_email":"askdocdb@microsoft.com","name":"azure-cosmos","package_url":"https://pypi.org/project/azure-cosmos/","platform":null,"project_url":"https://pypi.org/project/azure-cosmos/","project_urls":{"Homepage":"https://github.com/Azure/azure-sdk-for-python"},"provides_extra":null,"release_url":"https://pypi.org/project/azure-cosmos/4.9.0/","requires_dist":["azure-core>=1.30.0","typing-extensions>=4.6.0"],"requires_python":">=3.8","summary":"Microsoft Azure Cosmos Client Library for Python","version":"4.9.0","yanked":false,"yanked_reason":null}

Dependencies of azure-cosmos (2).
Dependency	Optional
azure-core	false
typing-extensions	false

Package search

azure-cosmos

project_urls

Dependencies

All package metadata

Releases