Merge pull request #252886 from seesharprun/cosmos-issue-resolution-1

Cosmos DB | Bulk issue resolutions #1

Author: prmerger-automator[bot]

articles/cosmos-db/burst-capacity-faq.yml

@@ -51,7 +51,7 @@ sections:
       - question: |
           How can I enable burst capacity on an account programatically?
         answer: |
-          You can use the [Azure Cosmos DB Resource Provider REST API version 2022-11-15-preview](/rest/api/cosmos-db-resource-provider/) or a [Resource Manager template](manage-with-templates.md) with API version 2022-11-15-preview to set the property **enableBurstCapacity** to true.
+          You can use the [Azure Cosmos DB Resource Provider REST API version `2023-03-15-preview`](/rest/api/cosmos-db-resource-provider/2023-03-15-preview/database-accounts/create-or-update) or a [Resource Manager template with API version `2023-03-01-preview`](/azure/templates/microsoft.documentdb/2023-03-01-preview/databaseaccounts) to set the property `enableBurstCapacity` to true.
           You can also use the Azure CLI or PowerShell.
 
           #### [PowerShell](#tab/azure-powershell)

articles/cosmos-db/gremlin/quickstart-python.md

@@ -32,17 +32,11 @@ In this quickstart, you create and manage an Azure Cosmos DB for Gremlin (graph)
   You can also install the Python driver for Gremlin by using the `pip` command line:
 
    ```bash
-   pip install gremlinpython==3.4.13
+   pip install gremlinpython==3.7.*
    ```
 
 - [Git](https://git-scm.com/downloads).
 
-> [!NOTE]
-> This quickstart requires a graph database account created after December 20, 2017. Existing accounts will support Python once they’re migrated to general availability.
-
-> [!NOTE]
-> We currently recommend using gremlinpython==3.4.13 with Gremlin (Graph) API as we haven't fully tested all language-specific libraries of version 3.5.* for use with the service.
-
 ## Create a database account
 
 Before you can create a graph database, you need to create a Gremlin (Graph) database account with Azure Cosmos DB.

articles/cosmos-db/mongodb/connect-using-mongoose.md

@@ -56,10 +56,10 @@ After you create the database, you'll use the name in the `COSMOSDB_DBNAME` envi
 
 3. Install the necessary packages using one of the ```npm install``` options:
 
-   * **Mongoose**: ```npm install mongoose@5.13.15 --save```
+   * **Mongoose**: ```npm install mongoose --save```
 
-     > [!IMPORTANT]
-     > The Mongoose example connection below is based on Mongoose 5+, which has changed since earlier versions. Azure Cosmos DB for MongoDB is compatible with up to version `5.13.15` of Mongoose. For more information, please see the [issue discussion](https://github.com/Automattic/mongoose/issues/11072) in the Mongoose GitHub repository.
+    > [!NOTE]
+    > For more information on which version of mongoose is compatible with your API for MongoDB server version, see [Mongoose compatability](https://mongoosejs.com/docs/compatibility.html).
     
    * **Dotenv** *(if you'd like to load your secrets from an .env file)*: ```npm install dotenv --save```
 

articles/cosmos-db/monitor-resource-logs.md

@@ -56,7 +56,7 @@ Here, we walk through the process of creating diagnostic settings for your accou
     | **GremlinRequests** | Gremlin | Logs user-initiated requests from the front end to serve requests to Azure Cosmos DB for Gremlin. When you enable this category, make sure to disable DataPlaneRequests. | `operationName`, `requestCharge`, `piiCommandText`, `retriedDueToRateLimiting` |
     | **QueryRuntimeStatistics** | NoSQL | This table details query operations executed against an API for NoSQL account. By default, the query text and its parameters are obfuscated to avoid logging personal data with full text query logging available by request. | `databasename`, `partitionkeyrangeid`, `querytext` |
     | **PartitionKeyStatistics** | All APIs | Logs the statistics of logical partition keys by representing the estimated storage size (KB) of the partition keys. This table is useful when troubleshooting storage skews. This PartitionKeyStatistics log is only emitted if the following conditions are true: 1. At least 1% of the documents in the physical partition have same logical partition key. 2. Out of all the keys in the physical partition, the PartitionKeyStatistics log captures the top three keys with largest storage size. </li></ul> If the previous conditions aren't met, the partition key statistics data isn't available. It's okay if the above conditions aren't met for your account, which typically indicates you have no logical partition storage skew. **Note**: The estimated size of the partition keys is calculated using a sampling approach that assumes the documents in the physical partition are roughly the same size. If the document sizes aren't uniform in the physical partition, the estimated partition key size may not be accurate. | `subscriptionId`, `regionName`, `partitionKey`, `sizeKB` |
-    | **PartitionKeyRUConsumption** | API for NoSQL | Logs the aggregated per-second RU/s consumption of partition keys. This table is useful for troubleshooting hot partitions. Currently, Azure Cosmos DB reports partition keys for API for NoSQL accounts only and for point read/write and stored procedure operations. | `subscriptionId`, `regionName`, `partitionKey`, `requestCharge`, `partitionKeyRangeId` |
+    | **PartitionKeyRUConsumption** | API for NoSQL | Logs the aggregated per-second RU/s consumption of partition keys. This table is useful for troubleshooting hot partitions. Currently, Azure Cosmos DB reports partition keys for API for NoSQL accounts only and for point read/write, query, and stored procedure operations. | `subscriptionId`, `regionName`, `partitionKey`, `requestCharge`, `partitionKeyRangeId` |
     | **ControlPlaneRequests** | All APIs | Logs details on control plane operations, which include, creating an account, adding or removing a region, updating account replication settings etc. | `operationName`, `httpstatusCode`, `httpMethod`, `region` |
     | **TableApiRequests** | API for Table | Logs user-initiated requests from the front end to serve requests to Azure Cosmos DB for Table. When you enable this category, make sure to disable DataPlaneRequests. | `operationName`, `requestCharge`, `piiCommandText` |
 

articles/cosmos-db/nosql/how-to-use-stored-procedures-triggers-udfs.md

@@ -564,7 +564,7 @@ The following code shows how to call a post-trigger using the Python SDK:
 ```python
 item = {'category': 'Personal', 'name': 'Groceries',
         'description': 'Pick up strawberries', 'isComplete': False}
-container.create_item(item, {'post_trigger_include': 'trgPreValidateToDoItemTimestamp'})
+container.create_item(item, pre_trigger_include='trgPreValidateToDoItemTimestamp')
 ```
 
 ---

articles/cosmos-db/nosql/performance-tips-query-sdk.md

@@ -91,7 +91,17 @@ The SQL SDK includes a native ServiceInterop.dll to parse and optimize queries l
 
 # [V3 .NET SDK](#tab/v3)
 
-For queries that target a Partition Key by setting the [PartitionKey](/dotnet/api/microsoft.azure.cosmos.queryrequestoptions.partitionkey) property in `QueryRequestOptions` and contain no aggregations (including Distinct, DCount, Group By):
+For queries that target a Partition Key by setting the [PartitionKey](/dotnet/api/microsoft.azure.cosmos.queryrequestoptions.partitionkey) property in `QueryRequestOptions` and contain no aggregations (including Distinct, DCount, Group By). In this example, the partition key field of `/state` is filtered on the value `Washington`.
+
+```csharp
+using (FeedIterator<MyItem> feedIterator = container.GetItemQueryIterator<MyItem>(
+    "SELECT * FROM c WHERE c.city = 'Seattle' AND c.state = 'Washington'"
+{
+    // ...
+}
+```
+
+Optionally, you can provide the partition key as a part of the request options object.
 
 ```cs
 using (FeedIterator<MyItem> feedIterator = container.GetItemQueryIterator<MyItem>(

articles/cosmos-db/nosql/quickstart-spark.md

@@ -675,7 +675,7 @@ The Azure Cosmos DB Spark 3 OLTP Connector for API for NoSQL has a complete conf
     az cosmosdb sql role assignment create --account-name $accountName --resource-group $resourceGroupName --scope "/" --principal-id $principalId --role-definition-id $readOnlyRoleDefinitionId
     ```
 
-1. Now that you have created an Azure Active Directory application and service principle, created a custom role, and assigned that role permissions to your Cosmos DB account, you should be able to run your notebook. 
+1. Now that you have created an Azure Active Directory application and service principal, created a custom role, and assigned that role permissions to your Cosmos DB account, you should be able to run your notebook. 
 
 ## Migrate to Spark 3 Connector