tDataEncrypt Standard properties

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 Sync columns to retrieve the schema from the previous component connected in the Job.

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.

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.

Password

This value must be enclosed in double quotes.

When using an existing cryptographic file, enter the password required to use this file.

When generating a cryptographic file, enter the password used to encrypt this file.

This password is required to decrypt back data using the tDataDecrypt component.

Cryptographic file path

When using an existing cryptographic file, enter the path to the cryptographic file. It must be enclosed in double quotes.

This cryptographic file is encrypted using AES-GCM.

This cryptographic file is required to decrypt back data using the tDataDecrypt component.

For more information about the cryptographic file, see the data encryption process.

Generate cryptographic file

Click this button to generate the cryptographic file.

Encryption

Select the corresponding Encrypt check boxes to encrypt input columns.

You can encrypt all column data types but the output encrypted data is of string type. Dynamic data type is only supported when it is the last row and when it comes from the input component. If you add it to the schema of tDataEncrypt, it is not supported. For more information, see Dynamic schema in your Talend Studio user guide.

Configure the output schema of the component to set the type of the columns to be encrypted to String.

When the input data is a null value, it will not be encrypted.

The columns that are not selected will not be encrypted and be returned as-is by the component.

tStat Catcher Statistics

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

Usage rule

This component is usually used as an intermediate component, and it requires an input component and an output component.