# tStandardizeRow properties for Apache Spark Structured Streaming

[Preview](https://help.qlik.com/en-US/cloud-services/Subsystems/Hub/Content/Sense_Hub/Introduction/feature-preview-program-overview.htm)

These properties are used to configure tStandardizeRow running in the Spark Structured Streaming Job framework.

The Spark Structured Streaming tStandardizeRow component belongs to the Data Quality family.

This component is supported on Local Spark 3.5.x and Databricks/EMR with Spark 3.x.

Information noteNote: This component does not support dynamic schema.

This component is available in Talend Real-Time Big Data Platform and Talend Data Fabric.

## Basic settings

| Properties | Description |
| --- | --- |
| Schema and Edit 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> </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> |
| Column to parse | Select the column to be parsed from the received data<br>flow |
| Standardize this field | Select this check box to standardize the rule-compliant<br>data identified, that is, to replace the duplicates of the identified<br>data with the corresponding standardized data from a given index.<br><br>For further information about this index providing<br>standardized data, see [tSynonymOutput](https://help.qlik.com/talend/en-US/components/8.0/synonym-index/tsynonymoutput).<br><br>Every time you select or clear this check box, the schema<br>of this component is changed automatically, so in a given Job, you need<br>to click the activated Sync<br>columns button to fix the inconsistencies in the<br>schema. |
| Generate analyzer code as routine | Click this button to enable the data parser of Talend Studio to recognize the rules defined in the Conversion<br>rules table.<br><br>In a given Job, when a rule is created, this operation is<br>required for the execution of this rule, while if it is on an existing<br>rule that you have modified, this operation is required only when the<br>modified rule is of type Enumeration, Format or Combination. For further information about all of the<br>rule types, see [Rule types](https://help.qlik.com/talend/en-US/components/8.0/standardization/tstandardizerow-tstandardizerow-rule-types-standard-component-enterprise-two). |
| ![](https://help.qlik.com/talend/en-US/components/8.0/Resources/images/import.png) and ![](https://help.qlik.com/talend/en-US/components/8.0/Resources/images/export.png) | Click the import or export button to exchange a given<br>standardization rule set with the DQ<br>Repository.<br><br>- When you click the export button, Talend Studio is switched to the Profiling perspective and the Parser rule<br>Settings view is opened on the workspace with the relative<br>contents filled automatically. Then if need be, you can edit the exported rule<br>set and save it to the Libraries &gt;<br>Rules &gt; Parser folder in the DQ<br>Repository tree view.<br><br>- When you click the import button, a import wizard is<br>opened to help you import the standardization rule of interest.<br><br>For further information, see [Setting and managing parser rules](https://help.qlik.com/talend/r/en-US/8.0/studio-user-guide/setting-and-managing-parser-rules). |
| Conversion rules | Define the rules you need to apply as the following:<br><br>- In the Name<br>column, type in a name of the rule you want to use. This name is used as<br>the XML tag or the JSON attribute name and the token name to label the<br>incoming data identified by this rule.<br><br>- In the Type<br>column, select the type of the rule you need to apply. For further<br>information about available rule types, see [Rule types](https://help.qlik.com/talend/en-US/components/8.0/standardization/tstandardizerow-tstandardizerow-rule-types-standard-component-enterprise-two).<br><br>- In the Value<br>column, type in the syntax of the rule.<br><br>- In the Search<br>mode column, select a search mode from the list. The<br>search modes can be used only with the Index rule type. For further information about<br>available search modes, see [Search modes for Index rules](https://help.qlik.com/talend/en-US/components/8.0/standardization/search-modes-for-index-rules).<br><br>- When you select the Index rule type, set the<br>path as follows:<br><br><ul> <li>In local mode:<ul> <li>Apache Spark 3.1 and earlier: <span>prefix://file                                                      path</span> or <span>file:///file                                                      path</span>.</li> <li>Apache Spark 3.2 and later: <span>file:///file path</span>.</li> </ul> </li> <li>In Standalone and Yarn modes: <span>prefix://file path</span>.</li> <li>If the index is on a cluster: <span>hdfs://hdpnameservice1/file path</span>.                                 </li> </ul><br><br>A test view is provided to help you create the parser rules of<br>interest. For further information, see [Setting and managing parser rules](https://help.qlik.com/talend/r/en-US/8.0/studio-user-guide/setting-and-managing-parser-rules). |

## Usage

| Usage guidance | Description |
| --- | --- |
| **Usage rule** | This component is used as an intermediate step.<br><br>This component, along with the Spark Structured Streaming component Palette it belongs to,<br>appears only when you are creating a Spark Structured Streaming Job. |
| Spark Connection | You need to use the Structured Streaming Configuration<br>tab in the Run view to define the connection to a Spark cluster for<br>the whole Job.<br><br>This connection is effective on a per-Job basis. |