Take back control

The type of questions that we get on the forums with regards to Pentaho Data Integration (Kettle) has been shifting lately from this type of question:

How do I read data from database type xxx

going to this type of questions:

I want to read a list of e-mail addresses from a database table, set a variable and send the warehouse log files off to all these people.

That’s quite an evolution that’s been going on. It’s obvious that people are starting to find the obvious solutions to the first type of questions so now they just get stuck on doing more complex things. I guess that’s to be expected, really. It’s nice that for the most part, I can now say, “yes, with the new 2.3.0 release, that is most certainly possible”
However, IMHO, often there is something missing at the implementers side of the story as well. I guess what I’m saying is that all too often these fine folks have been strugling so long with software limitations that they forget that it’s them that’s in charge, not the data, not the database, them.

So, as a guideline for Kettle development, this is what’s important to me. If it’s blocking for an BI implementer, it’s important. It’s as simple as that. That’s because I hate saying that something is not possible.

So the bottom line is: don’t let the data or the database get you down, take back control!

Example of variable use in Mail job entry