search

rpbouman / kettle-cookbook

Automatically exported from code.google.com/p/kettle-cookbook
GNU Lesser General Public License v3.0
46 stars 36 forks source link

Support for built-in variables #48

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
Hi!

You will find a doc file where I try to explain my problem.

Original issue reported on code.google.com by joseph.c...@gmail.com on 18 Jun 2012 at 8:32

Attachments:

GoogleCodeExporter commented 9 years ago 
Title should read: support for user variables. Built-in variables are to some 
extent supported.

Original comment by roland.bouman on 18 Jun 2012 at 11:02

joaociocca commented 9 years ago

from what I understand about the cookbook process, it just reads the jobs and transformations XML files, it won't execute, interpret or replace user variables - and I doubt it really should, actually...

rpbouman commented 9 years ago

Yeah it's a tough nut. One the one hand it is useful to replace some built-in variables - for example, I usually use job dir, trans dir and so on to keep related transformations and jobs together. I'd really like that to be picked up and documented all after expanding those vars.

But user vars are functional elements that can help make a job / transformation dynamic. If you push another value into those, you don't suddenly get a new job or trans that needs to be documented; rather, I would want to document the fact that a variable is used, not what people put into that variable.

Keeping the issue open in case someone else has thoughts on this.