Skip to main content Skip to complementary content

Azure Cosmos DB properties

Properties to configure to connect to an Azure Cosmos DB table.

Cosmos DB connection



Selection Select or enter CosmosDB.
Engine Select your engine in the list.
Main URI Enter the URI of your Azure Cosmos DB account.

The expected format is the following: https://<your_account>

For more information, read the Azure documentation on URI syntax.

Primary key Enter the primary key used to access your Azure Cosmos DB account.

It can be found in your Azure Cosmos DB account under Settings > Connection String.

Database ID Enter the name of the database you have created in your Azure Cosmos DB account.
Advanced Connection mode Specifies the connection mode to be used. Two options are available: Active and DirectHttps. Read the Azure documentation on ConnectionMode for more information.
Max connection pool size Sets the upper limit on the number of open files and so the total number of authorized connections. The default value is 1000.
Consistency level Defines the level of the consistency model, from strongest to weakest. Read the Azure documentation on Consistency levels for more information.
Description Enter a display name (mandatory) and a description (optional) for the connection.

Cosmos DB dataset

Property Configuration
Dataset name Enter a display name for the dataset. This name will be used as a unique identifier of the dataset in all Talend Cloud apps.
Connection Select your connection in the list. If you are creating a dataset based on an existing connection, this field is read-only.
Main Collection ID Enter the identifier of your Azure Cosmos DB collection.
Use query Select this option to retrieve data using query statements. You can enter the query statement in the Query field.

Additional JDBC parameters might be displayed depending on whether the connector is used as a source or destination dataset, read this section to know more about these parameters.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – let us know how we can improve!