tMapROjaiOutput Standard properties - 7.0


English (United States)
Talend Big Data
Talend Big Data Platform
Talend Data Fabric
Talend Open Studio for Big Data
Talend Real-Time Big Data Platform
Talend Studio
Data Governance > Third-party systems > NoSQL components > MapRDB components
Data Quality and Preparation > Third-party systems > NoSQL components > MapRDB components
Design and Development > Third-party systems > NoSQL components > MapRDB components

These properties are used to configure tMapROjaiOutput running in the Standard Job framework.

The Standard tMapROjaiOutput component belongs to the Databases family.

The component in this framework is available in all Talend products with Big Data and in Talend Data Fabric.

Basic settings

Property type

Either Built-In or Repository.

Built-In: No property data stored centrally.

Repository: Select the repository file where the properties are stored.


Enter the name of the table to be processed.

DB versions

Select the version of your database.

Use kerberos authentication

If you are accessing a MapR-DB as-OJAI database running with Kerberos security, select this check box, then, enter the Kerberos principal name and password in the displayed fields.

Every time when you launch your Job, the component submits this authentication information to Kerberos for a new kinit ticket.

  • If the MapR ticket security mechanism is also set up along with Kerberos, this component issues a mapr login command to obtain a MapR ticket at the same time.

  • If only the MapR ticket security mechanism is set up for your cluster while Kerberos is not, keep this check box clear. The component obtains a MapR ticket itself via your MapR Client.

Use a keytab to authenticate

Select the Use a keytab to authenticate check box to log into a Kerberos-enabled system using a given keytab file. A keytab file contains pairs of Kerberos principals and encrypted keys. You need to enter the principal to be used in the Principal field and the access path to the keytab file itself in the Keytab field. This keytab file must be stored in the machine in which your Job actually runs, for example, on a Talend Jobserver.

Note that the user that executes a keytab-enabled Job is not necessarily the one a principal designates but must have the right to read the keytab file being used. For example, the user name you are using to execute a Job is user1 and the principal to be used is guest; in this situation, ensure that user1 has the right to read the keytab file to be used.

Action on table

Select an operation to be performed on the table defined.

  • None: No operation is carried out.

  • Drop and create table: The table is removed and created again.

  • Create table: The table does not exist and gets created.

  • Create table if does not exist: The table is created if it does not exist.

  • Drop table if exist and create: The table is removed if it already exists and created again.

  • Truncate: The table content is deleted.

Action on data

Select an action to be performed on data of the table defined.

  • Insert: Add new entries to the table. If duplicates are found, job stops.

  • Replace: if the table already contains data, delete all the existing data and insert the new data. If the table is empty, insert the new data.

  • Insert or Replace: it looks at the document IDs, replaces the documents whose IDs exist in both the database and the data to be written, and inserts the documents whose IDs do not exist in the database.

  • Delete: Remove entries corresponding to the input flow.

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.

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

  • View schema: choose this option to view the schema only.

  • Change to built-in property: choose this option to change the schema to Built-in for local changes.

  • Update repository connection: choose this option to change the schema stored in the repository and decide whether to propagate the changes to all the Jobs upon completion. If you just want to propagate the changes to the current Job, you can select No upon completion and choose this schema metadata again in the [Repository Content] window.

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


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 the related description of retrieving table schemas in Talend Studio User Guide.

Bulk write

Select this check box to insert, update or remove data in bulk.

In the Bulk write size field, enter the size of each query group to be processed by MapR-DB.


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
first       "person"
last        "person"

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

tStatCatcher Statistics

Select this check box to gather the Job processing metadata at the Job level as well as at each component level.

Global Variables

Global Variables

ERROR_MESSAGE: the error message generated by the component when an error occurs. This is an After variable and it returns a string. This variable functions only if the Die on error check box is cleared, if the component has this check box.

NB_LINE: the number of rows read by an input component or transferred to an output component. This is an After variable and it returns an integer.

NB_LINE_REJECTED: the number of rows rejected. This is an After variable and it returns an integer.

A Flow variable functions during the execution of a component while an After variable functions after the execution of the component.

To fill up a field or expression with a variable, press Ctrl + Space to access the variable list and choose the variable to use from it.

For further information about variables, see Talend Studio User Guide.


Usage rule

tMapROjaiOutput executes the action defined on the documents in a given MapR-DB database based on the flow incoming from the preceding component in your Job.