tDataDecrypt properties for Apache Spark Streaming - Cloud - 8.0

Data privacy

Version
Cloud
8.0
Language
English
Product
Talend Big Data Platform
Talend Data Fabric
Talend Data Management Platform
Talend Data Services Platform
Talend MDM Platform
Talend Real-Time Big Data Platform
Module
Talend Studio
Content
Data Governance > Third-party systems > Data Quality components > Data privacy components
Data Quality and Preparation > Third-party systems > Data Quality components > Data privacy components
Design and Development > Third-party systems > Data Quality components > Data privacy components

These properties are used to configure tDataDecrypt running in the Spark Streaming Job framework.

The Standard tDataDecrypt component belongs to the Data Quality family.

The component in this framework is available in Talend Data Management Platform, Talend Big Data Platform, Talend Real Time Big Data Platform, Talend Data Services Platform, and in Talend Data Fabric.

Basic settings

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.

Secret method
Select the secret method used to encrypt the input data:
  • Cryptographic file
  • 256-bit key (encoded with base64)

Password

Available when Cryptographic file is selected as secret method.

Enter the password used to encrypt the cryptographic file generated by the tDataEncrypt component.

This value must be enclosed in double quotes.

Cryptographic file path

Available when Cryptographic file is selected as secret method.

Enter the path to the cryptographic file used to encrypt the input data with the tDataEncrypt component.

This value must be enclosed in double quotes.

Cryptographic method

Available when 256-bit key (encoded with base64) is selected as secret method.

Select the secret method used to encrypt the input data:
  • Cryptographic file
  • 256-bit key (encoded with base64)
Secret key

Available when 256-bit key (encoded with base64) is selected as secret method.

This value must be enclosed in double quotes.

Enter the key used to encrypt the input data.

Columns to decrypt

Select the corresponding Decrypt check boxes to decrypt input columns.

The columns that are not selected will not be decrypted. Properly configure the output schema of the component to set the type of the columns to be decrypted to String.

You cannot decrypt:
  • Unencrypted data.
  • Data encrypted without the tDataEncrypt component.
Die on error
Select this check box to stop the execution of the Job when an error occurs.
Important: When this check box is cleared, invalid input data will not be decrypted and will be kept as output data.

Advanced settings

Key derivation function Select the same key derivation function as to encrypt the data. By default, PBKDF2 with 300,000 iterations is selected.

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

Usage rule

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

Spark Connection

In the Spark Configuration tab in the Run view, define the connection to a given Spark cluster for the whole Job. In addition, since the Job expects its dependent jar files for execution, you must specify the directory in the file system to which these jar files are transferred so that Spark can access these files:
  • Yarn mode (Yarn client or Yarn cluster):
    • When using Google Dataproc, specify a bucket in the Google Storage staging bucket field in the Spark configuration tab.

    • When using HDInsight, specify the blob to be used for Job deployment in the Windows Azure Storage configuration area in the Spark configuration tab.

    • When using Altus, specify the S3 bucket or the Azure Data Lake Storage for Job deployment in the Spark configuration tab.
    • When using on-premise distributions, use the configuration component corresponding to the file system your cluster is using. Typically, this system is HDFS and so use tHDFSConfiguration.

  • Standalone mode: use the configuration component corresponding to the file system your cluster is using, such as tHDFSConfiguration or tS3Configuration.

    If you are using Databricks without any configuration component present in your Job, your business data is written directly in DBFS (Databricks Filesystem).

This connection is effective on a per-Job basis.