Skip to main content

To Iterate or Flow in Talend Open Studio

When working with RDBMS or Web Services components, Talend Open Studio jobs use Flows.  For systems programming -- file operations, etc. -- jobs use Iterators.  Use a Flow where possible, but keep things as Iterate if most of the components are Iterate connection-based.

In Talend Open Studio, looping or repeating actions are formed using either Flows or Iterators.  To bridge the two, there are adapter components: tIterateToFlow, tFlowToIterate.

Take the following job as an example

Two Forms of Repeating Actions in TOS
Iterate

Two tFileLists are used to drive the processing (a System.out.println).  The first tFileList uses the Iterate connector fed into a tJava.  For each file found in the tFileList, the tJava is invoked.  No data is sent to the tJava.  The tJava accesses a global variable available after each tFileList iteration.

tJava Code Iterate Connector
Flow

To convert the list of files into a Flow where each file is a row, use the tIterateToFlow adapter.  This requires defining a schema that will be filled in the Mapping section of the tIterateToFlow adapter.

Single Column Schema of a tIterateToFlow
Because the tFileList is converted to a Flow, accessing global variables isn't needed.  The data is available using the standard 'row' syntax like this.  This means that Flow-based components like tFilterRow can be used most effectively (recording the number of rows processed, etc.).

Flow-based Code Displaying tFileList
Depending on your Job, you have flexibility in selecting an Iterate or Flow.  There are adapters that convert from one to the other.  One rule of thumb in making your selection is if your job would benefit from having a structured schema associated with you iteration-based components.  In this post, a single-field schema is used to transport the values from the tFileList.  This could be expanded to additional values.

Comments

Post a Comment

Popular posts from this blog

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...
132 comments
Read more

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 ...
Post a Comment
Read more

Synchronous and Asynchronous execution in ODI

In data warehouse designing, an important step is to deciding which step is before/after. Newly added packages and required DW data must be analyzed carefully. Synchronous addings can lengthen ETL duration. Interfaces, procedures without generated scenario cannot be executed in parallel. Only scenario executions can be parallel in ODI. Default scenario execution is synch in ODI. If you want to set a scenario to executed in parallel then you will write “-SYNC_MODE=2″ on command tab or select Synchronous / Asynchronous option Asynchronous in General tab. I have created a package as interfaces executes as; INT_JOBS parallel  INT_REGIONS synch  INT_REGIONS synch  INT_COUNTRIES synch  INT_LOCATIONS parallel  INT_EMPLOYEES parallel (Interfaces are independent.) Selecting beginning and ending times and durations from repository tables as ODI 11g operator is not calculating these values. It is obvious in ODI 10g operator. SELECT    sess_no...
Post a Comment
Read more