Component family |
Custom Code |
|
Function |
tSetDynamicSchema allows you to |
|
Purpose |
tSetDynamicSchema is used to |
|
Basic settings |
Schema and Edit |
A schema is a row description. It defines the number of fields to be processed and passed on Since version 5.6, both the Built-In mode and the Repository mode are |
|
|
Built-In: You create and store the schema locally for this |
|
|
Repository: You have already created the schema and |
Click Edit schema to make changes to the schema. If the
|
||
Sync columns | Click to synchronize the output file schema with the input file schema. The Sync function is available only when the component is linked with an input component using a Row connection. |
|
Parameters |
This table contains two columns.
Property: Property of the schema
Value: Value assigned to this |
|
Advanced settings |
tStatCatcher Statistics |
Select this check box to gather the Job processing metadata at a |
Global Variables |
DYNAMIC: the last row of the data retrieved using the ERROR_MESSAGE: the error message generated by the A Flow variable functions during the execution of a component while an After variable To fill up a field or expression with a variable, press Ctrl + For further information about variables, see Talend Studio |
|
Usage |
This component is generally used as the end component in a |
|
Log4j |
The activity of this component can be logged using the log4j feature. For more information on this feature, see Talend Studio User For more information on the log4j logging levels, see the Apache documentation at http://logging.apache.org/log4j/1.2/apidocs/org/apache/log4j/Level.html. |
|
Limitation |
This component always requires an input component to defines the NoteTo work with tSetDynamicSchema, components should have the |
For a related scenario that uses the tSetDynamicSchema component, see Scenario 2: Handling a positional file based on a dynamic schema of the tFileInputPositional component.