tDenormalize Standard properties
These properties are used to configure tDenormalize running in the Standard Job framework.
The Standard tDenormalize component belongs to the Processing family.
The component in this framework is available in all Talend products.
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 Edit schema to make changes to the schema. If the current schema is of the Repository type, three options are available:
|
|
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. |
|
To denormalize | In this table, define the parameters used to denormalize your columns.
|
Advanced settings
Null value as an empty string in concatenation | Select this check box to convert null values to empty strings. If an input column in the To denormalize table is null, and the column output type is "String", the null value is replaced with an empty string. |
tStatCatcher Statistics | Select this check box to collect the log data at component level. Note that this check box is not available in the Map/Reduce version of the component. |
Global Variables
Global Variables |
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. 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. 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 more information about variables, see Using contexts and variables. |
Usage
Usage rule | This component can be used as intermediate step in a data flow. |
Limitation | Note that this component may change the order in the incoming Java flow. |