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.

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

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

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
Talend Studio

User Guide.

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.

• The Record type of BigQuery is not supported.
• The columns for table metadata such as the Description column or the Mode column cannot be retrieved.
• The Timestamp data from your BigQuery system is formated to be
  String data.
• The numeric data of BigQuery is converted to BigDecimal.

File name

Browse, or enter the path to the .txt or .csv file
you need to generate.

Append

Select the check box to write new data at the end of the existing
data. Otherwise, the existing data will be overwritten.

Field Separator

Enter character, string or regular expression to separate fields for the transferred
data.

Select this check box to create the directory you defined in the
File field for Google Cloud Storage, if it
does not exist.

Custom the flush buffer size

Enter the number of rows to be processed before the memory is freed.

Check disk space

Select the this check box to throw an exception during execution
if the disk is full.

Encoding

Select the encoding from the list or select Custom
and define it manually. This field is compulsory for database data handling. The
supported encodings depend on the JVM that you are using. For more information, see
https://docs.oracle.com.

tStatCatcher Statistics

Select this check box to collect the log data at the component
level/

Global Variables

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.

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.

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

This is an output component which needs the data provided by its
preceding component.

This component automatically detects and
supports both multi-regional locations and regional locations. When using the
regional locations, the buckets and the datasets to be used must be in the same
locations.