{"id":330,"date":"2009-01-30T14:31:30","date_gmt":"2009-01-30T21:31:30","guid":{"rendered":"http:\/\/www.nicholasgoodman.com\/bt\/blog\/?p=330"},"modified":"2009-01-30T14:31:30","modified_gmt":"2009-01-30T21:31:30","slug":"the-death-of-prevrow-rowclone","status":"publish","type":"post","link":"http:\/\/www.nicholasgoodman.com\/bt\/blog\/2009\/01\/30\/the-death-of-prevrow-rowclone\/","title":{"rendered":"The death of prevRow = row.clone()"},"content":{"rendered":"

UPDATE: This step is available in <\/strong>Kettle 3.2 M1.<\/a><\/strong><\/p>\n

For those that have done more involved Kettle projects you’ll know how valuable the Javascript step is. It’s the Swiss Army knife of Kettle development. The calculator step is a nice thought, but the limited set of functions and the constriction of having to enter it in pulldowns can make more complex calculations more difficult.<\/p>\n

Those that have done “observed metric” type calculations in Kettle will know this bit of Javascript well:<\/p>\n

var prevRow;
\nvar PREV_ORDER_DATE;<\/p>\n

if ( prevRow != null && prevRow.getInteger(“customernumber”, -1) == customernumber.getInteger() )
\nPREV_ORDER_DATE = prevRow.getDate(“orderdate”, null);
\nelse
\nPREV_ORDER_DATE = null;<\/p>\n

prevRow = row.Clone();<\/strong><\/p><\/blockquote>\n

This little bit of Javascript allowed you to “look forward” (or back depending on your sorting) and calculate the difference between items:<\/p>\n