# tPredictCluster properties for Apache Spark Streaming 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 tPredictCluster running in the Spark Streaming Job framework. The Spark Streaming tPredictCluster component belongs to the Machine Learning family. This component is available in Talend Real Time Big Data Platform and Talend Data Fabric. ## Basic settings | 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. When you create a Spark
Job, avoid the reserved word line when naming the
fields.

Click Edit
schema to make changes to the schema. If the current schema is of the Repository type, three options are available:

View schema: choose this option to view the schema only.
Change to built-in property: choose this option to change the schema to Built-in for local changes.
Update repository connection: choose this option to change the schema stored in the repository and decide whether to propagate the changes to all the Jobs upon completion. If you just want to propagate the changes to the current Job, you can select No upon completion and choose this schema metadata again in the Repository Content window.

Note that the schema of this component is read-only. Its single column LABEL is used to load the class names from the classifier model
for use in the classification process. | | --- | --- | | Model on filesystem | Select this radio box if the model to be used is stored on a file system. The button for
browsing does not work with the Spark Local mode; if you
are using the Spark Yarn or the Spark Standalone mode, ensure that you have properly configured the connection in
a configuration component in the same Job, such as tHDFSConfiguration.

In the HDFS
folder field that is displayed, enter the HDFS URI in which this model is
stored. | | Model computed in the current Job | Select this radio box and then select the model training component that is used in the
same Job to create the model to be used. | ## Usage | **Usage rule** | This component is used as an intermediate step. | | --- | --- | | Spark Connection | In the Spark
Configuration tab in the Run
view, define the connection to a given Spark cluster for the whole Job. In
addition, since the Job expects its dependent jar files for execution, you must
specify the directory in the file system to which these jar files are
transferred so that Spark can access these files:

Yarn mode (Yarn client or Yarn cluster):
- When using Google Dataproc, specify a bucket in the Google Storage staging bucket field in the Spark configuration tab.
- When using HDInsight, specify the blob to be used for Job deployment in the Windows Azure Storage configuration area in the Spark configuration tab.
- When using Altus, specify the S3 bucket or the Azure Data Lake Storage for Job deployment in the Spark configuration tab.
- When using Qubole, add a tS3Configuration to your Job to write your actual business data in the S3 system with Qubole. Without tS3Configuration, this business data is written in the Qubole HDFS system and destroyed once you shut down your cluster.
- 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 tHDFSConfiguration.
Standalone mode: use the configuration component corresponding to the file system your cluster is using, such as tHDFSConfiguration Apache Spark Batch or tS3Configuration Apache Spark Batch.

If you are using Databricks without any configuration component present in your Job, your business data is written directly in DBFS (Databricks Filesystem).

This connection is effective on a per-Job basis. |