Hi!
- I have a couple of jobs A and B that require two named parameters: "url" and "database" (defined without default value)
- every job calls a transformation "config", passing it the two parameters, then "config" calls a webservice and sets a bunch of variables in the root
when calling A and B from kitchen, passing "url" and "database" as named parameters in the cmdline, everything is fine: the values are there and the webservice gets called correctly
To do some testing in spoon, I have defined "url" and "database" in kettle.properties (to act as a sort of global defaults for all the jobs that require these as named parameters), but when running A or B from inside spoon, the values of "url" and "database" are emptied!
Is it normal that a variable, defined in kettle.properties, if accessed in a job that requires the same variable (defined with no default), loses its value?
- I have a couple of jobs A and B that require two named parameters: "url" and "database" (defined without default value)
- every job calls a transformation "config", passing it the two parameters, then "config" calls a webservice and sets a bunch of variables in the root
when calling A and B from kitchen, passing "url" and "database" as named parameters in the cmdline, everything is fine: the values are there and the webservice gets called correctly
To do some testing in spoon, I have defined "url" and "database" in kettle.properties (to act as a sort of global defaults for all the jobs that require these as named parameters), but when running A or B from inside spoon, the values of "url" and "database" are emptied!
Is it normal that a variable, defined in kettle.properties, if accessed in a job that requires the same variable (defined with no default), loses its value?