tChangeFileEncoding Standard properties
These properties are used to configure tChangeFileEncoding running in the Standard Job framework.
The Standard tChangeFileEncoding component belongs to the Data Quality and the File families.
The component in this framework is available in all Talend products.
Basic settings
Use Custom Input Encoding |
Select this check box to customize input encoding type. When it is selected, a list of input encoding types appears, allowing you to select an input encoding type or specify an input encoding type by selecting CUSTOM. |
Encoding |
From this list of character encoding types, you can select one of the offered options or customize the character encoding by selecting CUSTOM and specifying a character encoding type. |
Input File Name |
Path of the input file. |
Output File Name |
Path of the output file. |
Buffer Size |
Specify the buffer size (in bytes) for changing the file encoding. A proper buffer size improves the changing performance. This field defaults to 8192. |
Advanced settings
Create directory if does not exist |
This check box is selected by default. It creates a directory to hold the output table if required. |
tStatCatcher Statistics |
Select this check box to collect log data at the component level. |
Global Variables
Global Variables |
EXISTS: the result of whether a specified file exists. This is a Flow variable and it returns a Boolean. FILENAME: the name of the file processed. This is an After variable and it returns a string. 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 more information about variables, see Using contexts and variables. |
Usage
Usage rule |
This component can be used as standalone component. |