|
Property type
|
Either Built-In or Repository.
Built-In: No property data stored centrally.
Repository: Select the repository file where the
properties are stored.
|
|
Table
|
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.
-
Update or insert: Update the record with the
given reference. If the record does not exist in the index pool, a new record would be
inserted.
-
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. The schema is either Built-In or stored remotely in the Repository.
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. Related topic: see
Talend Studio
User Guide.
|
| |
Repository: You have already created
the schema and stored it in the Repository. You can reuse it in various projects and
Job designs. Related topic: see
Talend Studio
User Guide.
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.
You can find more details about how to verify default
values in retrieved schema in Talend Help Center (https://help.talend.com).
|
|
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.
|
|
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" |
|
|
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.
|