refresh and edits

JustPies · JustPies · commit 870c06b8d1bb · 2023-03-14T15:08:08.000-04:00
diff --git a/articles/cosmos-db/nosql/bulk-executor-dotnet.md b/articles/cosmos-db/nosql/bulk-executor-dotnet.md
@@ -7,16 +7,17 @@ ms.service: cosmos-db
 ms.subservice: nosql
 ms.devlang: csharp
 ms.topic: how-to
-ms.date: 05/02/2020
+ms.date: 03/14/2023
 ms.reviewer: mjbrown
 ms.custom: devx-track-csharp, ignite-2022
 ---
 
 # Use the bulk executor .NET library to perform bulk operations in Azure Cosmos DB
+
 [!INCLUDE[NoSQL](../includes/appliesto-nosql.md)]
 
 > [!NOTE]
-> This bulk executor library described in this article is maintained for applications using the .NET SDK 2.x version. For new applications, you can use the **bulk support** that is directly available with the [.NET SDK version 3.x](tutorial-dotnet-bulk-import.md) and it does not require any external library. 
+> This bulk executor library described in this article is maintained for applications using the .NET SDK 2.x version. For new applications, you can use the **bulk support** that is directly available with the [.NET SDK version 3.x](tutorial-dotnet-bulk-import.md) and it does not require any external library.
 
 > If you are currently using the bulk executor library and planning to migrate to bulk support on the newer SDK, use the steps in the [Migration guide](how-to-migrate-from-bulk-executor-library.md) to migrate your application.
 
@@ -48,9 +49,9 @@ The "BulkImportSample" application generates random documents and bulk imports t
 
 ## <a id="bulk-import-data-to-an-azure-cosmos-account"></a>Bulk import data to an Azure Cosmos DB account
 
-1. Navigate to the "BulkImportSample" folder and open the "BulkImportSample.sln" file.  
+1. Navigate to the "BulkImportSample" folder and open the "BulkImportSample.sln" file.
 
-2. The Azure Cosmos DB's connection strings are retrieved from the App.config file as shown in the following code:  
+1. The Azure Cosmos DB's connection strings are retrieved from the App.config file as shown in the following code:
 
    ```csharp
    private static readonly string EndpointUrl = ConfigurationManager.AppSettings["EndPointUrl"];
@@ -62,7 +63,7 @@ The "BulkImportSample" application generates random documents and bulk imports t
 
    The bulk importer creates a new database and a container with the database name, container name, and the throughput values specified in the App.config file.
 
-3. Next the DocumentClient object is initialized with Direct TCP connection mode:  
+1. Next the DocumentClient object is initialized with Direct TCP connection mode:
 
    ```csharp
    ConnectionPolicy connectionPolicy = new ConnectionPolicy
@@ -74,7 +75,7 @@ The "BulkImportSample" application generates random documents and bulk imports t
    connectionPolicy)
    ```
 
-4. The BulkExecutor object is initialized with a high retry value for wait time and throttled requests. And then they're set to 0 to pass congestion control to BulkExecutor for its lifetime.  
+1. The BulkExecutor object is initialized with a high retry value for wait time and throttled requests. And then they're set to 0 to pass congestion control to BulkExecutor for its lifetime.
 
    ```csharp
    // Set retry options high during initialization (default values).
@@ -89,7 +90,7 @@ The "BulkImportSample" application generates random documents and bulk imports t
    client.ConnectionPolicy.RetryOptions.MaxRetryAttemptsOnThrottledRequests = 0;
    ```
 
-5. The application invokes the BulkImportAsync API. The .NET library provides two overloads of the bulk import API - one that accepts a list of serialized JSON documents and the other that accepts a list of deserialized POCO documents. To learn more about the definitions of each of these overloaded methods, refer to the [API documentation](/dotnet/api/microsoft.azure.cosmosdb.bulkexecutor.bulkexecutor.bulkimportasync).
+1. The application invokes the BulkImportAsync API. The .NET library provides two overloads of the bulk import API - one that accepts a list of serialized JSON documents and the other that accepts a list of deserialized POCO documents. To learn more about the definitions of each of these overloaded methods, refer to the [API documentation](/dotnet/api/microsoft.azure.cosmosdb.bulkexecutor.bulkexecutor.bulkimportasync).
 
    ```csharp
    BulkImportResponse bulkImportResponse = await bulkExecutor.BulkImportAsync(
@@ -101,8 +102,8 @@ The "BulkImportSample" application generates random documents and bulk imports t
      cancellationToken: token);
    ```
    **BulkImportAsync method accepts the following parameters:**
-   
-   |**Parameter**  |**Description** |
+
+   |**Parameter** |**Description** |
    |---------|---------|
    |enableUpsert    |   A flag to enable upsert operations on the documents. If a document with the given ID already exists, it's updated. By default, it's set to false.      |
    |disableAutomaticIdGeneration    |    A flag to disable automatic generation of ID. By default, it's set to true.     |
@@ -113,7 +114,7 @@ The "BulkImportSample" application generates random documents and bulk imports t
    **Bulk import response object definition**
    The result of the bulk import API call contains the following attributes:
 
-   |**Parameter**  |**Description**  |
+   |**Parameter** |**Description** |
    |---------|---------|
    |NumberOfDocumentsImported (long)   |  The total number of documents that were successfully imported out of the total documents supplied to the bulk import API call.       |
    |TotalRequestUnitsConsumed (double)   |   The total request units (RU) consumed by the bulk import API call.      |
@@ -124,9 +125,9 @@ The "BulkImportSample" application generates random documents and bulk imports t
 
 You can update existing documents by using the BulkUpdateAsync API. In this example, you'll set the `Name` field to a new value and remove the `Description` field from the existing documents. For the full set of supported update operations, refer to the [API documentation](/dotnet/api/microsoft.azure.cosmosdb.bulkexecutor.bulkupdate).
 
-1. Navigate to the "BulkUpdateSample" folder and open the "BulkUpdateSample.sln" file.  
+1. Navigate to the "BulkUpdateSample" folder and open the "BulkUpdateSample.sln" file.
 
-2. Define the update items along with the corresponding field update operations. In this example, you'll use `SetUpdateOperation` to update the `Name` field and `UnsetUpdateOperation` to remove the `Description` field from all the documents. You can also perform other operations like increment a document field by a specific value, push specific values into an array field, or remove a specific value from an array field. To learn about different methods provided by the bulk update API, refer to the [API documentation](/dotnet/api/microsoft.azure.cosmosdb.bulkexecutor.bulkupdate).
+1. Define the update items along with the corresponding field update operations. In this example, you'll use `SetUpdateOperation` to update the `Name` field and `UnsetUpdateOperation` to remove the `Description` field from all the documents. You can also perform other operations like increment a document field by a specific value, push specific values into an array field, or remove a specific value from an array field. To learn about different methods provided by the bulk update API, refer to the [API documentation](/dotnet/api/microsoft.azure.cosmosdb.bulkexecutor.bulkupdate).
 
    ```csharp
    SetUpdateOperation<string> nameUpdate = new SetUpdateOperation<string>("Name", "UpdatedDoc");
@@ -143,7 +144,7 @@ You can update existing documents by using the BulkUpdateAsync API. In this exam
    }
    ```
 
-3. The application invokes the BulkUpdateAsync API. To learn about the definition of the BulkUpdateAsync method, refer to the [API documentation](/dotnet/api/microsoft.azure.cosmosdb.bulkexecutor.ibulkexecutor.bulkupdateasync).  
+1. The application invokes the BulkUpdateAsync API. To learn about the definition of the BulkUpdateAsync method, refer to the [API documentation](/dotnet/api/microsoft.azure.cosmosdb.bulkexecutor.ibulkexecutor.bulkupdateasync).
 
    ```csharp
    BulkUpdateResponse bulkUpdateResponse = await bulkExecutor.BulkUpdateAsync(
@@ -154,7 +155,7 @@ You can update existing documents by using the BulkUpdateAsync API. In this exam
    ```  
    **BulkUpdateAsync method accepts the following parameters:**
 
-   |**Parameter**  |**Description** |
+   |**Parameter** |**Description** |
    |---------|---------|
    |maxConcurrencyPerPartitionKeyRange    |   The maximum degree of concurrency per partition key range, setting this parameter to null will make the library to use the default value(20).   |
    |maxInMemorySortingBatchSize    |    The maximum number of update items pulled from the update items enumerator passed to the API call in each stage. For the in-memory sorting phase that happens before bulk updating, setting this parameter to null will cause the library to use the default minimum value(updateItems.count, 1000000).     |
@@ -163,23 +164,23 @@ You can update existing documents by using the BulkUpdateAsync API. In this exam
    **Bulk update response object definition**
    The result of the bulk update API call contains the following attributes:
 
-   |**Parameter**  |**Description** |
+   |**Parameter** |**Description** |
    |---------|---------|
    |NumberOfDocumentsUpdated (long)    |   The number of documents that were successfully updated out of the total documents supplied to the bulk update API call.      |
    |TotalRequestUnitsConsumed (double)   |    The total request units (RUs) consumed by the bulk update API call.    |
    |TotalTimeTaken (TimeSpan)   | The total time taken by the bulk update API call to complete the execution. |
-    
-## Performance tips 
+
+## Performance tips
 
 Consider the following points for better performance when using the bulk executor library:
 
-* For best performance, run your application from an Azure virtual machine that is in the same region as your Azure Cosmos DB account's write region.  
+* For best performance, run your application from an Azure virtual machine that is in the same region as your Azure Cosmos DB account's write region.
 
-* It's recommended that you instantiate a single `BulkExecutor` object for the whole application within a single virtual machine that corresponds to a specific Azure Cosmos DB container.  
+* It's recommended that you instantiate a single `BulkExecutor` object for the whole application within a single virtual machine that corresponds to a specific Azure Cosmos DB container.
 
-* A single bulk operation API execution consumes a large chunk of the client machine's CPU and network IO (This happens by spawning multiple tasks internally). Avoid spawning multiple concurrent tasks within your application process that execute bulk operation API calls. If a single bulk operation API call that is running on a single virtual machine is unable to consume the entire container's throughput (if your container's throughput > 1 million RU/s), it's preferred to create separate virtual machines to concurrently execute the bulk operation API calls.  
+* A single bulk operation API execution consumes a large chunk of the client machine's CPU and network IO (This happens by spawning multiple tasks internally). Avoid spawning multiple concurrent tasks within your application process that execute bulk operation API calls. If a single bulk operation API call that is running on a single virtual machine is unable to consume the entire container's throughput (if your container's throughput > 1 million RU/s), it's preferred to create separate virtual machines to concurrently execute the bulk operation API calls.
 
-* Ensure the `InitializeAsync()` method is invoked after instantiating a BulkExecutor object to fetch the target Azure Cosmos DB container's partition map.  
+* Ensure the `InitializeAsync()` method is invoked after instantiating a BulkExecutor object to fetch the target Azure Cosmos DB container's partition map.
 
 * In your application's App.Config, ensure **gcServer** is enabled for better performance
   ```xml  
@@ -202,4 +203,4 @@ Consider the following points for better performance when using the bulk executo
 
 ## Next steps
 
-* To learn about the NuGet package details and the release notes, see the [bulk executor SDK details](sdk-dotnet-bulk-executor-v2.md).
+* To learn about the NuGet package details and the release notes, see [.NET bulk executor library: Download information (Legacy)](sdk-dotnet-bulk-executor-v2.md).
