This scenario applies only to Talend Platform products with Big Data and Talend Data Fabric.
For more technologies supported by Talend, see Talend components.
This Job uses tNLPPreprocessing to divide the input text into tokens. Then, the tokens are converted to the CoNLL format using tNormalize. You will be able to use this CoNLL file to learn a classification model for extracting named entities in text data.
Preparing a text sample by dividing it into tokens. The tokens will be used for training a classification model.
Learning a classification model, designing the features and evaluating the model.
For an example of how to generate a classification model using tNLPModel, see Generating a classification model.
You can find an example of how to generate a named entity recognition model on Talend Help Center (https://help.talend.com).
Applying the model on the full text to extract named entities using tNLPPredict.
For an example of how to extract named entities using a classification model, Extracting named entities using a classification model.
You can find an example of how to extract named entities using a classification model on Talend Help Center (https://help.talend.com).
For further information about natural language processing, see Natural Language Processing using Talend Studio.
You can find more information about natural language processing on Talend Help Center (https://help.talend.com).
tHDFSConfiguration is used in this scenario by Spark to connect to the HDFS system where the jar files dependent on the Job are transferred.
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.
If you are using Databricks without any configuration component present in your Job, your business data is written directly in DBFS (Databricks Filesystem).