July 30, 2023

tPredict – Docs for ESB 7.x

  2. Talend for ESB Docs
  3. Docs 7.x
  4. tPredict – Docs for ESB 7.x

tPredict

Predicts the situation of an element.

Based on the models generated by the classification
components, the clustering components or the regression components, tPredict predicts the situation an element could fall into. tPredict uses a given classification, clustering or
relationship model to analyse datasets incoming from its preceding component.

In local mode, Apache Spark 1.3.0, 1.4.0, 1.5.0, 1.6.0, 2.0.0, 2.3.0 and 2.4.0 are
supported.

Depending on the Talend
product you are using, this component can be used in one, some or all of the following
Job frameworks:

tPredict properties for Apache Spark Batch

These properties are used to configure tPredict running in the Spark Batch Job framework.

The Spark Batch
tPredict component belongs to the Machine Learning family.

The component in this framework is available in all Talend Platform products with Big Data and in 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.

Depending on the model you select to use, a corresponding read-only column is
automatically added to the schema and is used to carry the result records of the
prediction.

Model type

Select the type of the model you want tPredict to use.
This automatically adds a read-only column to the schema of tPredict to carry the result records of the prediction.

Define a storage configuration
component

Select the configuration component to be used to provide the configuration
information for the connection to the target file system such as HDFS.

If you leave this check box clear, the target file system is the local
system.

The configuration component to be used must be present in the same Job.
For example, if you have dropped a tHDFSConfiguration component in the Job, you can select it to write
the result in a given HDFS system.

The Define a storage configuration component check box is
displayed when you select this radio box. Select it to connect to the filesystem to be
used.

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.

The Define a storage configuration component check box is
displayed when you select this radio box. Select it to connect to the filesystem to be
used.

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.

This component, along with the Spark Batch component Palette it belongs to,
appears only when you are creating a Spark Batch Job.

Note that in this documentation, unless otherwise explicitly stated, a
scenario presents only Standard Jobs, that is to
say traditional
Talend
 data integration Jobs.

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-premise
      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 or
    tS3Configuration.

    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.

Related scenario

For a scenario in which tPredict is used, see Modeling the accident-prone areas in a city.

tPredict properties for Apache Spark Streaming

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

The Spark Streaming
tPredict 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.

Depending on the model you select to use, a corresponding read-only column is
automatically added to the schema and is used to carry the result records of the
prediction.

Model type

Select the type of the model you want tPredict to use.
This automatically adds a read-only column to the schema of tPredict to carry the result records of the prediction.

Define a storage configuration
component

Select the configuration component to be used to provide the configuration
information for the connection to the target file system such as HDFS.

If you leave this check box clear, the target file system is the local
system.

The configuration component to be used must be present in the same Job.
For example, if you have dropped a tHDFSConfiguration component in the Job, you can select it to write
the result in a given HDFS system.

The Define a storage configuration component check box is
displayed when you select this radio box. Select it to connect to the filesystem to be
used.

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.

The Define a storage configuration component check box is
displayed when you select this radio box. Select it to connect to the filesystem to be
used.

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.

This component, along with the Spark Streaming component Palette it belongs to, appears
only when you are creating a Spark Streaming Job.

Note that in this documentation, unless otherwise explicitly stated, a scenario presents
only Standard Jobs, that is to say traditional
Talend
 data
integration Jobs.

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-premise
      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 or
    tS3Configuration.

    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.

Related scenarios

No scenario is available for the Spark Streaming version of this component
yet.

Document get from Talend https://help.talend.com
Thank you for watching.
Docs 7.x
Subscribe
Notify of
guest
0 Comments
Inline Feedbacks
View all comments
0
Would love your thoughts, please comment.x
()
x