August 16, 2023

tTransliterate – Docs for ESB 6.x

  2. Talend for ESB Docs
  3. Docs 6.x
  4. tTransliterate – Docs for ESB 6.x

tTransliterate

Converts strings from many languages of the world to a standard set of characters
(Universal Coded Character Set, UCS).

This is a phonetic operation where the tTransliterate component attempts to create in UCS an equivalent of the
original string based on the sounds the string represents.

This component encodes text expressed in many of the world’s writing systems to readable
characters based on the repertoire of the Unicode Standard. This makes it easier for you
to recognize and interpret words from different languages than if the letters are left
in the original script. For further information about Unicode and Unicode Standard,
check Unicode and Unicode Standard.

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

tTransliterate Standard properties

These properties are used to configure tTransliterate running in the Standard Job framework.

The Standard
tTransliterate component belongs to the Data Quality family.

The component in this framework is available when you have subscribed to one of
the Talend Platform products or Talend Data
Fabric.

Basic settings

Schema

A schema is a row description. It defines the number of fields (columns) to
be processed and passed on to the next component. The schema is either Built-In or stored remotely in the Repository.

 

Built-In: You create and store the
schema locally for this component only. Related topic: see
Talend Studio

User Guide.

 

Repository: You have already created
the schema and stored it in the Repository. You can reuse it in various projects and
Job designs. Related topic: see
Talend Studio

User Guide.

Edit Schema

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.

Transliteration

This table lists the columns defined in the schema of the tTransliterate component.

Select the Transliterate check box
next to the column(s) of which you want to convert the content to
readable standard set of characters.

Advanced settings

tStatCatcher Statistics

Select this check box to collect log data at the component
level.

Global Variables

Global Variables

ERROR_MESSAGE: the error message generated by the
component when an error occurs. This is an After variable and it returns a string. This
variable functions only if the Die on error check box is
cleared, if the component has this check box.

A Flow variable functions during the execution of a component while an After variable
functions after the execution of the component.

To fill up a field or expression with a variable, press Ctrl +
Space to access the variable list and choose the variable to use from it.

For further information about variables, see
Talend Studio

User Guide.

Usage

Usage rule

This component is an intermediary step. It requires an input and
output flows.

Scenario: Converting words from different languages to standard set of characters

This scenario applies only to a subscription-based Talend Platform solution or Talend Data Fabric.

This scenario describes a Job which uses:

  • the tFixedFlowInput component to generate the
    data you want to process,

  • the tTransliterate component to encode initial
    data expressed in different languages to readable characters based on the repertoire
    of the Unicode Standard,

  • the tFileOutputExcel component to output
    converted data in an .xls file.

use_case-ttransliterate.png

Setting up the Job

  1. Drop the following components from the Palette onto the design workspace: tFixedFlowInput, tTransliterate and
    tFileOutputExcel.
  2. Connect the three components together using the Main links.

Configuring the input component

  1. Double-click tFixedFlowInput to open its
    Basic settings view in the Component tab.

    use_case-ttransliterate2.png

  2. Create the schema through the Edit Schema
    button.

    In the open dialog box, click the [+] button
    and add the columns that will hold input data. For this example, add
    column1, column2,
    column3 and column4. The first two
    columns hold names written in different languages.
  3. Click OK.
  4. In the Number of rows field, enter
    1.
  5. In the Mode area, select the Use Inline Content option.
  6. In the Content table, enter the data you want
    to convert to readable characters based on the Unicode Standard repertoire as
    shown in the above image.

Transliterating data

  1. Double-click tTransliterate to display the
    Basic settings view and define the component
    properties.

    use_case-ttransliterate3.png

  2. If required, click Sync columns to retrieve
    the schema defined in the input component.

    In this example, only the first two columns are processed. You can click the
    Edit schema button to open the schema dialog
    box and see the input and output schemas.
    use_case-ttransliterate4.png

  3. In the Transliteration table of the component
    basic settings view, select the check boxes next to the columns you want to
    convert to standard characters.

Configuring the output component and executing the Job

  1. Double-click the tFileOutputExcel component
    to display the Basic settings view and define
    the component properties.

    use_case-ttransliterate5.png

  2. Set the destination file name as well as the sheet name and then select the
    Define all columns auto size check box.
  3. Save your Job and press F6 to execute
    it.

    The tTransliterate component encodes input
    data to readable characters based on the repertoire of the Unicode
    Standard.
  4. Right-click the output component and select Data
    Viewer     to display the transliterated data.

    use_case-ttransliterate6.png

    All names written in characters from diverse languages have been phonetically
    converted to a standard set of characters based on the Universal Coded Character
    Set, UCS. For example, the names in the first and second rows in the below image
    have been changed to Ragnarr,Lodbrok and to
    Routse,Anna respectively.
    use_case-ttransliterate7.png

    For further information about
    Unicode and Unicode Standards, check Unicode and Unicode
    Standard    .

tTransliterate properties for Apache Spark Batch

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

The Spark Batch
tTransliterate component belongs to the Data Quality family.

The component in this framework is available when you have subscribed to any Talend Platform product with Big Data or Talend Data
Fabric.

Basic settings

Schema

A schema is a row description. It defines the number of fields (columns) to
be processed and passed on to the next component. The schema is either Built-In or stored remotely in the Repository.

 

Built-In: You create and store the
schema locally for this component only. Related topic: see
Talend Studio

User Guide.

 

Repository: You have already created
the schema and stored it in the Repository. You can reuse it in various projects and
Job designs. Related topic: see
Talend Studio

User Guide.

Edit Schema

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.

Transliteration

This table lists the columns defined in the schema of the tTransliterate component.

Select the Transliterate check box
next to the column(s) of which you want to convert the content to
readable standard set of characters.

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

You need to use the Spark Configuration tab in
the Run view to 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: when using Google
    Dataproc, specify a bucket in the Google Storage staging
    bucket     field in the Spark
    configuration     tab; when using other distributions, use a
    tHDFSConfiguration
    component to specify the directory.

  • Standalone mode: you need to choose
    the configuration component depending on the file system you are using, such
    as tHDFSConfiguration
    or tS3Configuration.

This connection is effective on a per-Job basis.

Related scenarios

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

tTransliterate properties for Apache Spark Streaming

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

The Spark Streaming
tTransliterate component belongs to the Data Quality family.

The component in this framework is available only if you have subscribed to Talend Real-time Big Data Platform or Talend Data
Fabric.

Basic settings

Schema

A schema is a row description. It defines the number of fields (columns) to
be processed and passed on to the next component. The schema is either Built-In or stored remotely in the Repository.

 

Built-In: You create and store the
schema locally for this component only. Related topic: see
Talend Studio

User Guide.

 

Repository: You have already created
the schema and stored it in the Repository. You can reuse it in various projects and
Job designs. Related topic: see
Talend Studio

User Guide.

Edit Schema

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.

Transliteration

This table lists the columns defined in the schema of the tTransliterate component.

Select the Transliterate check box
next to the column(s) of which you want to convert the content to
readable standard set of characters.

Usage

Usage rule

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

This component is used as an intermediate step.

You need to use the Spark Configuration tab in the
Run view to define the connection to a given Spark cluster
for the whole Job.

This connection is effective on a per-Job basis.

For further information about a
Talend
 Spark Streaming Job, see the sections
describing how to create, convert and configure a
Talend
 Spark Streaming Job of the

Talend Open Studio for Big Data Getting Started
Guide
.

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

You need to use the Spark Configuration tab in
the Run view to 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: when using Google
    Dataproc, specify a bucket in the Google Storage staging
    bucket     field in the Spark
    configuration     tab; when using other distributions, use a
    tHDFSConfiguration
    component to specify the directory.

  • Standalone mode: you need to choose
    the configuration component depending on the file system you are using, such
    as tHDFSConfiguration
    or tS3Configuration.

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 6.x
Subscribe
Notify of
guest
0 Comments
Inline Feedbacks
View all comments
0
Would love your thoughts, please comment.x
()
x