Skip to main content

Comparing 2 File Lists in Talend Open Studio

This post uses the add() and remove() Java Collections calls to the set difference of two lists of files.  Files from 2 directories are listed and one directory's files are removed from the other.  The result is a difference used in later processing.

java.util.List.add() and List.remove() can gather the results of a tFileList for later processing.  Pulling in a library like Commons Collections, these lists can be easily searched, sorted, transformed, and operated on with a variety of set-based operations (intersection, subtraction, etc.).

tFileList produces an iteration that can be converted to a flow using the tIterateToFlow.  The flow can then drive a tJavaRow.  The tIterateToFlow has the benefit of conveniently defining a flow schema.  The schema in this example is a single field (the full file path), but could be extended with additional columns for the other variables produced by tFileList.

Job Comparing 2 Directories' Files
tSetGlobalVar

The job starts with a tSetGlobalVar, listed as "Init Builder List".  You may have seen examples of setting variables of simple types like "FileName" set to "C:\data\file1.txt".  This job sets a variable that is a Java object which will be unpacked in the other components.

Use the following as the Key and Value of the tSetGlobalVar component.  There are no quotes around the 'new' statement.

"builderList" / new ArrayList<String>() 

tFileList

Both tFileLists -- "List csv files" and "List txt files" -- are standard.  They are searching for files of pattern "*.csv" and "*.txt".  (In a production job, these components should use context variables that parameterize the directory.  

tFlowToIterate

The tFlowToIterate components connect the tFileList with custom Java code (tJavaRow).  The tFlowToIterates defined a single-field schema.  If additional file list information were needed, the schema could be expanded to include other tFileList variables.

tFlowToIterate Configuration
 Both tFlowToIterate components are similar except for the tFileList source.

tJavaRow

Two tJavaRows work with the list using the following algorithm.
  1. Strip the suffix from a CSV file
  2. Add the CSV file (minus the .csv) to the builderList
  3. Strip the suffix from a TXT file
  4. Remove the file name from builderList
  5. The result is a list of suffix-less filenames 
Add to builder list

This component uses the following tJavaRow code

List<String> builderList = (List<String>)globalMap.get("builderList");
builderList.add( row1.filename.substring(0, row1.filename.length() -4) );

In the Advanced settings tab, java.util.List is imported.  (There is a line that can be uncommented.)

Remove from builder list

The second tJavaRow component uses

List<String> builderList = (List<String>)globalMap.get("builderList");
builderList.remove(row2.filename.substring(0, row2.filename.length()-4));

 

Remaining Work

The job ends with the execution of a tJava.  This tJava can deal with the build-up lists or could be replaced with another set of iteration components.

You can always integrate large blocks of Java code into Talend for some functionality that's missing off-the-shelf.  However, it's usually more maintainable to keep the jobs as standard as possible.  If you do choose to write Java code, try packaging the Java code in a routine or component rather than embedding chunks throughout the job. 

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

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