Manipulating a tHashOutput in Talend Open Studio

The Talend Open Studio tHashOutput and tHashInput allow you to save your input in RAM, offering potential performance gains. The basic usage defines a single tHashOutput which gathers input and a tHashInput which will direct the input to a data flow. This post describes two expanded configurations.

tHashOutput and tHashInput worked with input stored in internal memory and do so in a way consistent with other Talend components. The Hash components allow you to define flows to retrieve data throughout a map that has been stored by some other part of the job. In a simple scenario, this is done with a single input/output pair.

Multiple Sources

This screenshot shows a job that will merge two data sources -- a tRowGenerator and a tFileInputDelimited -- into a single Hash data structure using two tHashOutputs. The first tHashOutput will be referenced by subsequent tHashOutputs in the "Link with a tHashOutput" control.

Configuration of Linked tHashOutput

This tHashOutput refers to the first component.

tHashOutput Referring to Prior Component

The combined data sets are available through the tHashInput. It doesn't matter which of the two components are selected in the Component List select since they are linked.

tHashInput Configuration

Neither the Data Write Model, Keys Management, or Append settings will have any effect in this job. Data Write Model has only one value in its select. I think Keys Management has a bug in version 5 (see TDI-21180). Append only takes effect in an iteration.

Clearing When Iterating

This job iterates over a data set, clearing the backing RAM structure defined in the tHashOutput with each iteration. This is done by unchecking Append. If Append were not unchecked, each iteration would produce more and more output as the preceding iteration's tHashOutput gathers more values.

Clearing After Each Iteration

The results of clearing the tHashOutput follow.

Results with Append Unchecked

If Append is checked, the output is repeated as it accrues through the iterations.

Iterating in Append Mode

The tHashOutput and tHashInput components can provide your Talend Open Studio job with a performance gain by saving input in RAM. tHashOutput can be used to gather input from different sources using the Linked feature. Append mode will work only in iterations and provides control over when a tHashOutput is cleared.

Comments

ODI KM Adding Order by Option

You can add Order by statement to queries by editing KM.I have edited IKM SQL Control Append to provide Order by. 1) Add an option to KM named USE_ORDER_BY, its type is Checkbox and default value is False. This option determines you want an order by statement at your query. 2)Add second option to KM named ORDER_BY, type is Text. You will get order by values to your query by this option. 3) Editing Insert New Rows detail of KM. Adding below three line code after having clause. That's it! <% if (odiRef.getOption("USE_ORDER_ BY").equals("1")) { %> ORDER BY <%=odiRef.getOption("ORDER_BY" )%> <%} %> If USE_ORDER_BY option is not used, empty value of ORDER_BY option get error. And executions of KM appears as such below; At this execution, I checked the KM to not get errors if ORDER_BY option value is null. There is no prove of ORDER BY I'm glad. Second execution to get Ord

Creating Yellow Interface in ODI

Hello everyone! In Oracle data integrator (ODI), an interface is an object which populates one datastore, called the target , with data coming from one or more other datastores, known as sources . The fields of the source datastore are linked to those in the target datastore using the concept of Mapping . Temporary interfaces used in ODI are popularly known as Yellow Interfaces . It is because ODI generates a yellow icon at the time of creation of a yellow interface as opposed to the blue icon of a regular interface. The advantage of using a yellow interface is to avoid the creation of Models each time you need to use it in an interface. Since they are temporary, they are not a part of the data model and hence don’t need to be in the Model. So let’s begin and start creating our yellow interface! Pre-requisites : Oracle 10g Express Edition with *SQL Plus, Oracle Data Integrator 11g. Open *SQL Plus and create a new table Sales in Oracle. You can use any existing ta

Running Count in Talend Open Studio

Most Talend components keep a count of the records processed using variables like NB_LINE or NB_LINE_OK. But these are only available after all processing is completed. Define your own counter variable to keep a running count for use in a tMap. Variables like tFilterRow.NB_LINE or tAccessOutput.NB_LINE_INSERTED can be used to report the number of affected lines after a subjob's processing. However, it may be of use to get the current line index for use in a tMap. The index variables used to form NB_LINE aren't available during processing; they're only written out the globalMap at the end of processing. In this example, staging records are loaded from Excel to Access. The order in which the Excel records are read is preserved in a database column called DISPLAY_SEQ_NB. Note that there is an auto-increment column used for record ID in the Access table. This could be used to infer a loading order, but this job uses a separate column to keep the ID as a meaningless surr

TechWare

Search This Blog