Skip to main content

Shorthand Globals for Talend Open Studio

In Talend Open Studio, even with code complete, it's sometimes difficult to work with long strings for reading global variables.  Use a single function 'glstr' to reduce the clutter in your expressions.

Reading global variables in Java usually involves a cast, a variable, a method, and a key.  Using the technique in this blog post, this can be reduced to a method and a key.

The typical way of accessing a global,

(String)globalMap.get("SYSTEM_NAME")

Can be reduced to

glstr("SYSTEM_NAME")


Futhermore, this technique can serve as the basis for a useful library that provides a shorthand for other global access.  This can include other casting or data conversion.  Another function could be something like 'glint' which will either cast the global to an Integer, parse a String global into an Integer, or truncate a Double global.

Take the following Talend Open Studio Job.

Talend Open Studio Job with glstr Function
This job uses 5 components.
  • Init glstr. Import the GlobalUtils class and glstr function.  Initialize the GlobalUtils class with the Job's globalMap.
  • tSetGlobalVar. Set a global variable.
  • tForEach, tIterateToFlow, tLogRow.  Iterate over one row, writing out the global variable using glstr.
The following is the GlobalUtils routine.  It's created using the "Create routine" function.  See "User Defined Functions with Talend Open Studio" for instructions on how to do this.


package routines;

import java.util.HashMap;
import java.util.Map;

public class GlobalUtils {

   private static Map<String, Object> globalMap = new HashMap<String, Object>();

   public static void setGlobalMap(Map<String, Object> _globalMap) {
     globalMap = _globalMap;
   }

   public static String glstr(String _key) {
     return (String)globalMap.get(_key);
   }
}


Init glstr is a tJava that has entries in the "Basic settings" and "Advanced settings" tabs.  The following appears in Basic.

GlobalUtils.setGlobalMap( globalMap );


And the following appears in Advanced.  Notice the static import which lets you refer to glstr rather than GlobalUtils.glstr.


import routines.GlobalUtils;
import static routines.GlobalUtils.glstr;


tSetGlobalVar sets a single variable with Key="myglobal" and Value="someglobalvalue123".

The tIterateToFlow component actually invokes the glstr. Here is a screenshot showing the call. tIterateToFlow uses a single-field schema with a string column 'Field1'.

Talend Open Studio Calling 'glstr'
With a well-placed static import, commonly used functions can be reduced to a minimum of keystrokes.  A strategy like this can be very effective in larger tMaps where long expressions will scroll out-of-view.

Comments

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