Component family |
File/Input | |
Basic settings |
Property type |
Either Built-In or Repository. |
|
|
Built-In: No property data stored centrally. |
|
|
Repository: Select the repository file where the properties are stored. |
|
File Name/Stream |
File name: Name and path of the file to be processed. Stream: The data flow to be processed. The data must be added to the flow in order for tFileInputDelimited to fetch these data via the corresponding representative variable. This variable could be already pre-defined in your Studio or provided by the context or the components you are using along with this component; otherwise, you could define it manually and use it according to the design of your Job, for example, using tJava or tJavaFlex. In order to avoid the inconvenience of hand writing, you could select the variable of interest from the auto-completion list (Ctrl+Space) to fill the current field on condition that this variable has been properly defined.
Related topic to the available variables: see Talend Studio User Guide |
|
Row separator |
Enter the separator used to identify the end of a row. |
|
Field separator |
Enter character, string or regular expression to separate fields for the transferred data. |
|
CSV options |
Select this check box to include CSV specific parameters such as Escape char and Text enclosure. |
|
Header |
Enter the number of rows to be skipped in the beginning of file. |
|
Footer |
Number of rows to be skipped at the end of the file. |
|
Limit |
Maximum number of rows to be processed. If Limit = 0, no row is read or processed. |
|
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. The schema is either Built-In or stored remotely in the Repository. Click Edit schema to make changes to the schema. If the current schema is of the Repository type, three options are available:
Note that if the input value of any non-nullable primitive field is null, the row of data including that field will be rejected. |
|
|
Built-In: You create and store the schema locally for this component only. Related topic: see Talend Studio User Guide. |
|
|
Repository: You have already created the schema and stored it in the Repository. You can reuse it in various projects and Job designs. Related topic: see Talend Studio User Guide. |
|
Skip empty rows |
Select this check box to skip the empty rows. |
|
Uncompress as zip file |
Select this check box to uncompress the input file. |
|
Die on error |
Select this check box to stop the execution of the Job when an error occurs. Clear the check box to skip any rows on error and complete the process for error-free rows. When errors are skipped, you can collect the rows on error using a Row > Reject link. To catch the |
Advanced settings |
Advanced separator (for numbers) |
Select this check box to change the separator used for numbers. By default, the thousands separator is a comma (,) and the decimal separator is a period (.). |
|
Extract lines at random |
Select this check box to set the number of lines to be extracted randomly. |
|
Encoding |
Select the encoding from the list or select Custom and define it manually. This field is compulsory for database data handling. |
|
Trim all column |
Select this check box to remove the leading and trailing whitespaces from all columns. When this check box is cleared, the Check column to trim table is displayed, which lets you select particular columns to trim. |
|
Check each row structure against schema |
Select this check box to check whether the total number of columns in each row is consistent with the schema. If not consistent, an error message will be displayed on the console. |
|
Check date |
Select this check box to check the date format strictly against the input schema. |
|
Check columns to trim |
This table is filled automatically with the schema being used. Select the check box(es) corresponding to the column(s) to be trimmed. |
|
Split row before field |
Select this check box to split rows before splitting fields. |
|
Permit hexadecimal (0xNNN) or octal (0NNNN) for numeric types |
Select this check box if any of your numeric types (long, integer, short, or byte type), will be parsed from a hexadecimal or octal string. In the table that displays, select the check box next to the column or columns of interest to transform the input string of each selected column to the type defined in the schema. Select the Permit hexadecimal or octal check box to select all the columns. This table appears only when the Permit hexadecimal (0xNNN) or octal (0NNNN) for numeric types check box is selected. |
|
tStatCatcher Statistics |
Select this check box to gather the processing metadata at the Job level as well as at each component level. |
Global Variables |
NB_LINE: the number of rows processed. 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 |
Use this component to read a file and separate fields contained in this file using a defined separator. It allows you to create a data flow using a Row > Main link or via a Row > Reject link in which case the data is filtered by data that does not correspond to the type defined. For further information, please see Scenario 2: Extracting correct and erroneous data from an XML field in a delimited file. | |
Log4j |
If you are using a subscription-based version of the Studio, the activity of this component can be logged using the log4j feature. For more information on this feature, see Talend Studio User Guide. 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 |
Due to license incompatibility, one or more JARs required to use this component are not provided. You can install the missing JARs for this particular component by clicking the Install button on the Component tab view. You can also find out and add all missing JARs easily on the Modules tab in the Integration perspective of your studio. For details, see the article Installing External Modules on Talend Help Center (https://help.talend.com) how to configure the Studio in the Talend Installation and Upgrade Guide. |