tDeltaLakeInput properties for Apache Spark Batch

Select the configuration component to be used to provide the configuration information for the connection to the target file system.

If you leave this check box clear, the target file system is the local system.

The configuration component to be used must be present in the same Job. For example, if you have dropped a tS3Configuration component in the Job, you can select it to write the result in a given S3 storage system.

This field is available only when you select Files from the Define the source of the dataset drop-down list in the Basic settings view.

• Either Built-In or Repository.

• Built-In: No property data stored centrally.

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

  The properties are stored centrally under the Hadoop Cluster node of the Repository tree.

  The fields that come after are pre-filled in using the fetched data.

  For further information about the Hadoop Cluster node, see Managing Hadoop connection metadata.

• 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.

  Spark automatically infers data types for the columns in a PARQUET schema. In a Talend Job for Apache Spark, the Date type is inferred and stored as int96.

  This component offers the advantage of the dynamic schema feature. This allows you to retrieve unknown columns from source files or to copy batches of columns from a source without mapping each column individually. For further information about dynamic schemas, see Dynamic schema.

  This dynamic schema feature is designed for the purpose of retrieving unknown columns of a table and is recommended to be used for this purpose only; it is not recommended for the use of creating tables.

• 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.

This field is available only when you select Metastore from the Define the source of the dataset drop-down list in the Basic settings view.

This field is available only when you select Metastore from the Define the source of the dataset drop-down list in the Basic settings view.

Browse to, or enter the path pointing to the data to be used in the file system.

If you want to specify more than one files or directories in this field, separate each path using a comma (,).

The button for browsing does not work with the Spark Local mode; if you are using the other Spark Yarn modes that Talend Studio supports with your distribution, ensure that you have properly configured the connection in a configuration component in the same Job. Use the configuration component depending on the filesystem to be used.

This field is available only when you select Files from the Define the source of the dataset drop-down list in the Basic settings view.

This field is available only when you select SQL Query from the Define the source of the dataset drop-down list in the Basic settings view.

The format used by Deltalake is yyyy-MM-dd HH:mm:ss.

Delta Lake systematically creates slight differences between the upload time of a file and the metadata timestamp of this file. Bear in mind these differences when you need to filter data.

This property is only available if you select Files from the Define how to save the dataset drop-down list.

This property is only available if you select Files from the Define how to save the dataset drop-down list.

• Catalog: enter the name of the catalog to be used.
• Schema: enter the name of the schema to be used.
• Table: enter the name of the table to be used.

This component is used as an end component and requires an input link.

This Delta Lake layer is built on top of your Data Lake system, thus to be connected as part of your Data Lake system using the configuration component corresponding to your Data Lake system, for example, tAzureFSConfiguration.

This connection is effective on a per-Job basis.