PowerExchange for Microsoft Azure Cosmos DB SQL API User Guide

PowerExchange for Microsoft Azure Cosmos DB SQL API User Guide

Microsoft Azure Cosmos DB SQL API Data Object Write Operation Properties

Microsoft Azure Cosmos DB SQL API Data Object Write Operation Properties

Cosmos DB data object write operation properties include run-time properties that apply to the Cosmos DB collection you add in the Cosmos DB data object.
The Developer tool displays advanced properties for the Cosmos DB data object operation in the
Advanced
view. The following table describes the advanced properties for a Cosmos DB data object write operation:
Property
Description
Throughput (RU/s)
A positive integer and a multiple of 100. Request units processing per second. If you specify -1, the throughput is not altered during the write operation.
400 is the minimum throughput from the third party for a non-partition collection. 1000 is the minimum throughput from the third party for a partition collection.
If a Cosmos DB database has throughput shared among its collections, you cannot use the collections with Cosmos DB connector. You must use non-shared throughput collections with Cosmos DB connector.
Automatic ID Generation
Generate ID for the documents written to the target. Specify any of the following values:
  • Enabled. Cosmos DB generates IDs for the documents.
  • Disabled. The source object provides IDs for the documents. The Data Integration Service rejects the rows if a Null value is provided to the
    ID
    port in the target or if you do not connect a port to the
    ID
    port in target.
Treat Source Rows As
Operation to perform. You can select Insert, Update, Upsert, or Delete.
You must connect the ID port and Partition Key port to perform Update, Upsert, or Delete operations. The Data Integration Service displays an exception if you do not connect the ID port or the partition key for Upsert and Update operations, whereas, the Delete operation fails.
For Upsert and Update operations, in addition to the ports you want to update, you must connect all other ports a document contains. The values for the unconnected ports get deleted during Upsert and Update operations.
If you have a duplicate Partition Key and ID combination in the source rows, the mapping fails at the first occurrence of a bad record. The azure-cosmosdb-spark library throws an error and stops the mapping execution immediately.

0 COMMENTS

We’d like to hear from you!