Dear Kettle devs,

Over the weekend I received a question to deliver use-cases behind creating
transformations and jobs dynamically or automatically, as opposed to
creating them statically in Spoon.

Well obviously the number one case is the situation where you need to move
hundreds of database tables from one database to another. Let's say it's a
data staging exercise. Each table needs fields renamed and rejects from the
table output step need to be caught and put in a generic table somewhere so
we can put a small report on it.

This is the sort of thing that, even though it is really simple, can't be
solved with a classical transformation/job construction.

Now obviously a lot of folks wouldn't even think of building a generic
solution for this kind of situation. However, creating hundreds of
transformations by hand (each with the same logging configured and the same
input, select, output and rejects steps) is tedious and error prone work
that nobody likes to do. The loss of time in creating and maintaining this
set of transformations is also staggering.

The question to this list is then: do you know of other situations? Do you
perhaps want to populate your slowly changing dimensions straight from
metadata stored in a spreadsheet? Things like that?

Let us know, we're interested!

Matt Casters <mcasters (AT) pentaho (DOT) org>
Chief Data Integration, Kettle founder, Author of Pentaho Kettle
(Wiley <>)
Fonteinstraat 70, 9400 OKEGEM - Belgium - Cell : +32 486 97 29 37
Pentaho : The Commercial Open Source Alternative for Business Intelligence

You received this message because you are subscribed to the Google Groups "kettle-developers" group.
To post to this group, send email to kettle-developers (AT) googlegroups (DOT) com.
To unsubscribe from this group, send email to kettle-developers+unsubscribe (AT) g...oups (DOT) com.
For more options, visit this group at