A few days ago I had this idea: perhaps we could create a step that executes a job entry.

The parameters for the job entry could be variables that are set using input fields.
So the input is a field-to-variable mapping.

The output could be generic: the result, the result rows, the result files, etc.
Anything you want from the Result object really.

For example, you could be very flexible as far as the FTP job entry is concerned.
You could very easily loop over a number of FTP sites and get back the list of transferred files as a result to the next step that can automatically read them say with CSV Input.


All the best,

Matt Casters <mcasters (AT) pentaho (DOT) org>
Chief Data Integration
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) googlegroups (DOT) com
For more options, visit this group at http://groups.google.com/group/kettle-developers?hl=en