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...

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...

Oracle Data Integrator tools: OdiFileDelete and OdiOutFile

Hello everyone! It’s time for another cool ODI tutorial. Last time, I spoke about the   OdiZip tool and how it can be used to create zip files from a directory. Through this post, I will talk about two more tools related to  Files  namely  OdiFileDelete and  OdiOutFile . 1. OdiFileDelete The  OdiFileDelete  is a tool used to delete files present in a directory or a complete directory on the machine running the agent. Usage OdiFileDelete -DIR=<dir> | -FILE=<file> [-RECURSE=<yes|no>] [-CASESENS=<yes|no>] [-NOFILE_ERROR=<yes|no>] [-FROMDATE=<fromdate>] [-TODATE=<todate>] If  -FROMDATE  is omitted, all files with a modification date earlier than the  -TODATE  date will be deleted. If  -TODATE  is omitted, all files with a modification date later than the  -FROMDATE  date will be deleted. If both parameters are omitted, all files matching the  -FILE...