Microsoft Azure Cosmos DB Writer Parameters

About Database Connections

Database formats include a Database Connection parameter that defines and stores authentication information. For general information about sharing database connections, please see Using Database Connections. Using Database Connections.

Note that Database Connection parameters differ slightly, depending on context and/or database format.

Connection

From the Connection parameter in a database format, you can do one of the following:

  • Select an existing, previously defined connection. See the section Reusing a Database Connection in Using Database Connections
  • Select Add Database Connection to define a new connection. See database-specific parameters below, as well as the section Adding a Database Connection in a Workspace in Using Database Connections. The new connection can be made visible only to the current user, or can be shared among multiple users.

Database Connection

Select an existing Microsoft Azure Cosmos DB database connection, or Add Database Connection...

Add Microsoft Azure Cosmos DB Database Connection

To define a new connection from the Connection parameter in a Cosmos DB format, see the topic Microsoft Azure Cosmos DB: Add Database Connection

Advanced

To improve performance, the Cosmos DB writer issues requests concurrently. This parameter specifies how many requests may be in progress at once.

If your network and Collection provisioned throughput supports heavier usage, you can increase this number to improve performance. If writes are failing due to throttling, try reducing this number.

Default: 4

This parameter specifies the maximum number of times to reattempt a request that is rate-limited by the server. The server performs rate-limiting when the size and frequency of requests exceeds the Collection’s provisioned throughput.

If the request continues to be rate-limited after retrying for the specified number of times, the writer logs a warning and skips the request.

Default: 3

This parameter controls whether the writer should raise an error when the server rejects a feature write.

If this option is set to Yes, then the writer will stop writing features when it detects an HTTP error response from the Cosmos DB server.

Note  If multiple concurrent requests are enabled on the writer, it is still possible for features to be written after a failed write. Otherwise, features that are rejected by the server will be logged with a warning.

If a feature is rejected by the writer due to misconfigured input (for example, conflicting fme_db_operation), this will not cause the writer to stop the translation.

Default value for new writers – Yes

Note  Legacy writers without this option will behave as though this option is set to No.

Prior to FME 2022.0, web access through this format would automatically disable HTTPS Certificate verification when an SSL Error was received from the server. Now, this behavior must be explicitly enabled or disabled by this parameter.

The value of this parameter takes priority over the value of the Verify SSL Certificates parameter which might be defined by the Web Connection used with this format.