You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/cosmos-db/graph/bulk-executor-graph-dotnet.md
+18-16Lines changed: 18 additions & 16 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -28,6 +28,13 @@ It's now available in following flavors:
28
28
* An Azure subscription. You can create [a free Azure account here](https://azure.microsoft.com/free/?ref=microsoft.com&utm_source=microsoft.com&utm_medium=docs&utm_campaign=cosmos-db). Alternatively, you can create a Cosmos database account with [Try Azure Cosmos DB for free](https://azure.microsoft.com/try/cosmosdb/) without an Azure subscription.
29
29
* An Azure Cosmos DB Gremlin API database with an **unlimited collection**. The guide shows how to get started with [Azure Cosmos DB Gremlin API in .NET](./create-graph-dotnet.md).
30
30
* Git. For more information check out the [Git Downloads page](https://git-scm.com/downloads).
31
+
#### Clone
32
+
To run this sample, run the `git clone` command below:
The sample is available at path .\azure-cosmos-graph-bulk-executor\dotnet\src\
49
50
50
-
### Run
51
+
### Execute
51
52
Modify the following parameters as:
52
53
53
54
Parameter|Description
@@ -66,14 +67,22 @@ Download the full sample application in .NET from [here](https://github.com/Azur
66
67
67
68
The sample application is provided to illustrate how to use the GraphBulkExecutor package. Samples are available for using either the Domain object annotations or using the POJO objects directly. It's recommended, to try both approaches, to determine which better meets your implementation and performance demands.
68
69
70
+
### Clone
71
+
To run the sample, run the `git clone` command below:
The sample is available at .\azure-cosmos-graph-bulk-executor\java\
94
-
95
97
To run the sample, refer the configuration as follows and modify as needed:
96
98
### Configuration
97
99
@@ -104,7 +106,7 @@ The /resources/application.properties file defines the data required to configur
104
106
***sample.sql.partition.path**: If the container needs to be created, this value will be used to define the partitionKey path.
105
107
***sample.sql.allow.throughput**: The container will be updated to use the throughput value defined here. If you're exploring different throughput options to meet your performance demands, make sure to reset the throughput on the container when done with your exploration. There are costs associated with leaving the container provisioned with a higher throughput.
106
108
107
-
### Execute the sample
109
+
### Execute
108
110
109
111
Once the configuration is modified as per your environment, then run the command:
0 commit comments