Microsoft Azure Cosmos DB Writer Parameters

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.

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, see the topic Microsoft Azure Cosmos DB: Add Database Connection

Spatial

Coordinate systems may be extracted from input feature data sources, may come predefined with FME, or may be user-defined. FME allows different output and input coordinate systems, and performs the required coordinate conversions when necessary.

How FME Processes Coordinate Systems in the Workspace

If a coordinate system is specified in both the source format and the workspace, the coordinate system in the workspace is used. The coordinate system specified in the source format is not used, and a warning is logged. If a source coordinate system is not specified in the workspace and the format or system does not store coordinate system information, then the coordinate system is not set for the features that are read.

If a destination coordinate system is set and the feature has been tagged with a coordinate system, then a coordinate system conversion is performed to put the feature into the destination system. This happens right before the feature enters into the writer.

If the destination coordinate system was not set, then the features are written out in their original coordinate system.

If a destination coordinate system is set, but the source coordinate system was not specified in the workspace or stored in the source format, then no conversion is performed. The features are simply tagged with the output system name before being written to the output dataset.

For systems that know their coordinate system, the Coordinate System field will display Read from Source and FME will read the coordinate system from the source dataset. For most other input sources, the field will display Unknown (which simply means that FME will use default values). In most cases, the default value is all you'll need to perform the translation.

You can always choose to override the defaults and choose a new coordinate system. Select More Coordinate Systems from the drop-down menu to open the Coordinate System Gallery.

Changing a Reprojection

To perform a reprojection, FME typically uses the CS-MAP reprojection engine, which includes definitions for thousands of coordinate systems, with a large variety of projections, datums, ellipsoids, and units. However, GIS applications have slightly different algorithms for reprojecting data between different coordinate systems. To ensure that the data FME writes matches exactly to your existing data, you can use the reprojection engine from a different application.

Note  To use this feature, you must have a supported GIS application installed on your system (for example, Esri ArcGIS®).

To change the reprojection engine, Select Workspace Parameters > Spatial > Reprojection Engine. In the example shown, you can select Esri (but the selection here depends on your installed applications):

For more information, see the links below:

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.

Note  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.