# tCosmosDBOutput Inserts, updates, upserts or deletes documents in a Cosmos database collection based on the incoming flow from the preceding component in the Job. This component is not shipped with your Talend Studio by default. You need to install it using the Feature Manager. For more information, see [Installing features using the Feature Manager](https://help.qlik.com/talend/r/en-US/8.0/studio-user-guide/install-features-to-talend-studio). ## tCosmosDBOutput Standard properties These properties are used to configure tCosmosDBOutput running in the Standard Job framework. The Standard tCosmosDBOutput component belongs to the Cloud and the Databases families. The component in this framework is available in all Talend products with Big Data and in Talend Data Fabric. ## Basic settings | Properties | Description | | --- | --- | | Use existing connection | Select this check box and in the Component
List drop-down list, select the desired connection component to
reuse the connection details you already defined. | | API | Select the database API to be used. Then the corresponding parameters to be defined are displayed in the Component view.

In the current version of this component, only the MongoDB API is supported. For this reason, MongoDB database is often mentioned in the documentation of the CosmosDB components. | | Use replica set address or multiple query routers | Select this check box to show the Server
addresses table.

In the Server addresses
table, define the shared MongoDB databases or the MongoDB replica sets
you want to connect to. | | Server and Port | Enter the IP address and listening port of the database
server.

Available when the Use replica set
address or multiple query routers check box is not
selected. | | Database | Enter the name of the MongoDB database to be connected to. | | Set write concern | Select this check box to set the level of acknowledgement requested for write
operations. Then you need to select the level of this operation.

For further information, see the related MongoDB documentation on http://docs.mongodb.org/manual/core/write-concern/. | | Bulk write | Select this check box to insert, update or remove data in bulk. Note this feature is available only when the version of MongoDB you are using is 2.6+.

Then you need to select Ordered or Unordered to define how the MongoDB database processes the data
sent by Talend Studio.



In the Bulk write size field, enter the size of each
query group to be processed by MongoDB. In the documentation of MongoDB, some restrictions
and expected behaviors as to this size are explained. You can find the details on http://docs.mongodb.org/manual/core/bulk-write-operations/. | | Authentication mechanism | Among the mechanisms listed on the Authentication mechanism
drop-down list, the NEGOTIATE one is recommended if
you are not using Kerberos, because it automatically select the authentication mechanism
the most adapted to the MongoDB version you are using.

For details about the other mechanisms in this list, see [MongoDB Authentication](https://docs.mongodb.org/manual/reference/parameters/#param.authenticationMechanisms) from the MongoDB
documentation. | | Set Authentication database | If the username to be used to connect to MongoDB has been created in a specific
Authentication database of MongoDB, select this check box to enter the name of this
Authentication database in the Authentication database
field that is displayed.

For further information about the MongoDB Authentication database, see [User Authentication database](https://docs.mongodb.org/manual/core/security-users/#user-authentication-database). | | Username and Password | DB user authentication data.

To enter the password, click the [...] button
next to the password field, enter the password in double quotes in the pop-up dialog box,
and click OK to save the settings.

Available when the Use
authentication check box is selected.

If the security system you have selected from the Authentication mechanism dropdown list is Kerberos, you need to
enter the User principal, the Realm and the KDC
server fields instead of the Username and the Password
fields. | | Collection | Name of the collection in the database. | | Drop collection if exist | Select this check box to drop the collection if it already
exists. | | Action on data | The following operations are available:

| | Schema and Edit
Schema | A schema is a row description. It defines the number of fields
(columns) to be processed and passed on to the next component. When you create a Spark
Job, avoid the reserved word line when naming the
fields.


Built-In: You create and store the schema locally for this component
only.


Repository: You have already created the schema and stored it in the
Repository. You can reuse it in various projects and Job designs.

When the schema to be reused has default values that are
integers or functions, ensure that these default values are not enclosed within
quotation marks. If they are, you must remove the quotation marks manually.

For more information, see [Retrieving table schemas](https://help.qlik.com/talend/r/en-US/8.0/studio-user-guide/retrieving-table-schemas?tocId=_C1~eFOlN~GM_JR2qkBYZg).

Click Edit
schema to make changes to the schema. If the current schema is of the Repository type, three options are available:



Click Sync columns to retrieve the
schema from the previous component connected in the Job.

This component supports dynamic schema when inserting documents to a
collection. To use the dynamic schema feature, make sure the schema contains
only one column, with the DB column set to
\* and Type set to
String (if the input type is
String) or Object (if the input
type is Object).

Information noteNote:

| | Mapping | Each column of the schema defined for this component represents a field of the documents
to be read. In this table, you need to specify the parent nodes of these fields, if
any.

For example, in the document reading as
follows

```
{
_id: ObjectId("5099803df3f4948bd2f98391"),
person: { first: "Joe", last: "Walker" }
}
```


The
*first* and the *last*
fields have *person* as their parent node but the *\_id* field does not have any parent node. So once completed, this
Mapping table should read as
follows:

```
Column Parent node path
_id
first "person"
last "person"
```

Not available when the Generate JSON
Document check box is selected in Advanced settings. | | Die on error | This check box is cleared by default, meaning to skip the row on error
and to complete the process for error-free rows. | ## Advanced settings | Properties | Description | | --- | --- | | Generate JSON Document | Select this check box for JSON configuration:


Configure JSON Tree: click the
[...] button to open the interface
for JSON tree configuration. For more information, see [Configuring a JSON Tree](https://help.qlik.com/talend/en-US/components/8.0/processing/configuring-a-json-tree).


Create empty element if
needed: If the Related Column in the XML tree editor has null values, or if no
column is associated with the XML node, this option creates an open/close tag
in the expected place. This check box is selected by default.


Ignore service attributes for empty
elements: Select this option to prevent the component from
generating a node if the input node is null but has service attributes (such as
@type, @class, and @array). This option
is available when the Create empty element if
needed option is not selected.


Group by: click the [+] button to add lines and choose the input
columns for grouping the records.


Remove root node: select this check
box to remove the root node.


Data node and Query node (available for update and upsert actions):
type in the name of data node and query node configured on the JSON
tree.

These nodes are mandatory for update and upsert actions. They are
intended to enable the update and upsert actions though will not be
stored in the database.

Node (available for Set and
Upsert with set actions): specify the update operations
for specific JSON nodes. To add an update operation, click the plus button at
the bottom of this field, enter the update operator or select the update
operator from the drop-down list in the Node type
column, and enter the node name in double quotation marks in the
Node reference column. See [Update Operators](https://docs.mongodb.com/v4.4/reference/operator/update/) for information about update
operators.

Information noteNote: This field is available only when you have installed the
R2022-01 Talend Studio Monthly update or a later one delivered by Talend. For more information, check with your administrator. | | No query timeout | Select this check box to prevent MongoDB servers from stopping idle
cursors at the end of 10-minute inactivity of these cursors. In this
situation, an idle cursor will stay open until either the results of
this cursor are exhausted or you manually close it using the
cursor.close() method.

A cursor for MongoDB is a pointer to the result set of a query. By
default, that is to say, with this check box being clear, a MongoDB
server automatically stops idle cursors after a given inactivity period
to avoid excess memory use. For further information about MongoDB
cursors, see https://docs.mongodb.org/manual/core/cursors/. | | tStatCatcher Statistics | Select this check box to collect the log data at the component
level. | ## Usage | Usage guidance | Description | | --- | --- | | **Usage rule** | tCosmosDBOutput executes the action
defined on the collection in the database based on the flow
incoming from the preceding component in the Job. | | Limitation | |