# tAggregateRow properties for Apache Spark Streaming (deprecated)

Availability-note[Deprecated](https://help.talend.com/r/en-US/Cloud/labels-on-talend-help-center/availability-deprecated)

This content is deprecated.

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

Information noteDeprecation: Spark Streaming is deprecated beginning with the R2026-09 release. Use Spark Structured Streaming instead.

The Spark Streaming tAggregateRow component belongs to the Processing family.

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

## Basic settings

| Properties | Description |
| --- | --- |
| 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> </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> |
| Group by | <ul> <li> <p>Define the aggregation sets, the values of which will be used for                            calculations.</p> </li> <li> <p> <span>Output Column</span>: Select the column                            label in the list offered based on the schema structure you defined. You                            can add as many output columns as you wish to make more precise                            aggregations. </p> <p> Ex: Select Country to calculate an average of values for each country                            of a list or select Country and Region if you want to compare one                            country's regions with another country' regions.</p> </li> <li> <p> <span>Input Column</span>: Match the input column                            label with your output columns, in case the output label of the                            aggregation set needs to be different.</p> </li> </ul> |
| Operations | <ul> <li> <p>Select the type of operation along with the value to use for the                            calculation and the output field.</p> </li> <li> <p> <span>Output Column</span>: Select the destination                            field in the list.</p> <p> <span>Function</span>: Select the operator among:</p> </li> <li> <p> <span>Input column</span>: Select the input column                            from which the values are taken to be aggregated.</p> </li> <li> <p> <span>Ignore null values</span>: Select the check                            boxes corresponding to the names of the columns for which you want the                            NULL value to be ignored.</p> </li> </ul> |

## Advanced settings

| Properties | Description |
| --- | --- |
| Use financial precision, this is the max precision for "sum"<br>and "avg" operations, checked option heaps more memory and slower<br>than unchecked. | Select this check box to use a financial precision. This is a max<br>precision but consumes more memory and slows the processing.<br><br>Information noteWarning:<br><br><br>*We advise you to use the BigDecimal type for the output in<br>order to obtain precise results.* |
| Check type overflow (slower) | Checks the type of data to ensure that the Job doesn't crash. |
| Check ULP (Unit in the Last Place), ensure that a value will<br>be incremented or decremented correctly, only float and double<br>types. (slower) | Select this check box to ensure the most precise results possible for<br>the Float and Double types. |

## Usage

| Usage guidance | Description |
| --- | --- |
| **Usage rule** | This component is used as an intermediate step.<br><br>This component, along with the Spark Streaming component Palette it belongs to, appears<br>only when you are creating a Spark Streaming Job.<br><br>Note that in this documentation, unless otherwise explicitly stated, a scenario presents<br>only Standard Jobs, that is to say traditional<br>Talend<br>data<br>integration Jobs. |
| Spark Connection | In the Spark<br>Configuration tab in the Run<br>view, define the connection to a given Spark cluster for the whole Job. In<br>addition, since the Job expects its dependent jar files for execution, you must<br>specify the directory in the file system to which these jar files are<br>transferred so that Spark can access these files:<br><br><ul> <li> <div> <span>Yarn mode</span> (Yarn client or Yarn cluster):<ul> <li> <p>When using Google Dataproc, specify a bucket in the                                            <span>Google Storage staging bucket</span>                                        field in the <span>Spark configuration</span>                                        tab.</p> </li> <li> <p>When using HDInsight, specify the blob to be used for Job                                        deployment in the <span>Windows Azure Storage                                            configuration</span> area in the <span>Spark                                            configuration</span> tab.</p> </li> <li>When using Altus, specify the S3 bucket or the Azure                                    Data Lake Storage for Job deployment in the <span>Spark                                        configuration</span> tab.</li> <li> <p>When using on-premises distributions, use                                        the configuration component corresponding to the file system                                        your cluster is using. Typically, this system is HDFS and so                                        use <a href="https://help.qlik.com/talend/r/en-US/8.0/components/hdfs/thdfsconfiguration">tHDFSConfiguration</a>.</p> </li> </ul> </div> </li> <li> <p> <span>Standalone mode</span>: use the                            configuration component corresponding to the file system your cluster is                            using, such as <a href="https://help.qlik.com/talend/r/en-US/8.0/components/hdfs/thdfsconfiguration-properties-for-apache-spark-batch">tHDFSConfiguration Apache Spark Batch</a> or <a href="https://help.qlik.com/talend/r/en-US/8.0/components/amazon-s3/ts3configuration-properties-for-apache-spark-batch">tS3Configuration Apache Spark Batch</a>.</p> <p>If you are using Databricks without any configuration component present                            in your Job, your business data is written directly in DBFS (Databricks                            Filesystem).</p> </li> </ul><br><br>This connection is effective on a per-Job basis. |