# tExtractRegexFields Standard properties

These properties are used to configure tExtractRegexFields running in the Standard Job framework.

The Standard tExtractRegexFields component belongs to the Data Quality and the Processing families.

The component in this framework is available in all Talend products.

## Basic settings

| Properties | Description |
| --- | --- |
| Field to split | Select an incoming field from the Field to<br>split list to split. |
| Regex | Enter a regular expression according to the programming language<br>you are using. |
| Schema and Edit<br>Schema | <ul> <li> <p>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 <kbd>line</kbd> when naming the            fields.</p> <p>Click <span>Edit        schema</span> to make changes to the schema. If the current schema is of the <span>Repository</span> type, three options are available:</p> <ul> <li> <p> <span>View schema</span>: choose this                option to view the schema only.</p> </li> <li> <p> <span>Change to built-in property</span>:                choose this option to change the schema to <span>Built-in</span> for local changes.</p> </li> <li> <p> <span>Update repository connection</span>:                choose this option to change the schema stored in the repository and decide whether                to propagate the changes to all the Jobs upon completion.</p> <p>If you just want to                propagate the changes to the current Job, you can select <span>No</span> upon completion and choose this schema metadata                again in the <span>Repository Content</span>                window.</p> </li> </ul> <p> Click <span>Sync columns</span> to retrieve								the schema from the previous component connected in the Job.</p> <div><span>Information note</span><span>Warning:</span> <p>Make sure that the output schema does not contain any column									with the same name as the input column to be split. Otherwise,									the regular expression will not work as expected. </p> </div> </li> <li> <p> <span>Built-In</span>: You create and store the schema locally for this component                only.</p> </li> <li> <p> <span>Repository</span>: You have already created the schema and stored it in the                Repository. You can reuse it in various projects and Job designs.</p> </li> </ul> |

## Advanced settings

| Properties | Description |
| --- | --- |
| Die on error | Select the checkbox to stop the execution of the Job when an error<br>occurs.<br><br>Clear the checkbox to skip any rows on error and complete the process for<br>error-free rows. When errors are skipped, you can collect the rows on error using a Row &gt; Reject link. |
| Check each row structure against<br>schema | Select this check box to check whether the total number of columns<br>in each row is consistent with the schema. If not consistent, an<br>error message will be displayed on the console. |
| tStatCatcher Statistics | Select this check box to gather the processing metadata at the Job<br>level as well as at each component level. |

## Global Variables

| Variables | Description |
| --- | --- |
| Global Variables | ERROR\_MESSAGE: the error message generated by the<br>component when an error occurs. This is an After variable and it returns a string. This<br>variable functions only if the Die on error checkbox is<br>cleared, if the component has this checkbox.<br><br>A Flow variable functions during the execution of a component<br>while an After variable functions after the execution of the component.<br><br>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<br>it.<br><br>For more information about variables, see [Using contexts and variables](https://help.qlik.com/talend/r/en-US/8.0/studio-user-guide/contexts-and-variables). |

## Usage

| Usage guidance | Description |
| --- | --- |
| **Usage rule** | This component handles flow of data therefore it requires input<br>and output components. It allows you to extract data from a<br>delimited field, using a Row &gt;<br>Main link, and enables you to<br>create a reject flow filtering data which type does not match the<br>defined type. |