Hello,
I made a simple job getting a parameter write it to log and quit.
It's working fine with data integration but when i run the job in command line with kitchen, the parmeter is not set.
I got this issus with osx and linux.
Thanks for your help.
Hello,
I made a simple job getting a parameter write it to log and quit.
It's working fine with data integration but when i run the job in command line with kitchen, the parmeter is not set.
I got this issus with osx and linux.
Thanks for your help.
Well, you have to specify the parameter value as a kitchen parameter (-param:PARAMETER=VALUE)
Matt Casters, Chief Data Integration
Pentaho, Open Source Business Intelligence
http://www.pentaho.org -- mcasters@pentaho.org
Author of the book Pentaho Kettle Solutions by Wiley. Also available as e-Book and on the Kindle reading applications (iPhone, iPad, Android, Kindle devices, ...)
Join us on IRC server Freenode.net, channel ##pentaho
I am having the same issue:
Created a job with a parameter ZipFileName, default NONE. Added a write to log step with:
ZipFileName=${ZipFileName}
parameterjob.JPG
Run it:
/opt/pentaho/design-tools/pdi-ee-4.0.0-GA/kitchen.sh -norep -file=TestFile.kjb -level=Detailed -param:ZipFileName=ker.zip
Output: ZipFileName=NONE
Quoting the parameter had no impact:
/opt/pentaho/design-tools/pdi-ee-4.0.0-GA/kitchen.sh -file=/var/pdi-assets/bnsfldw/Cargowise/TestFile.kjb "-param:ZipFileName=ker.zip"
No benefits from making the parameter name all upper-case (it is linux after all) or removing the extra options from the comman line.
Ok, this is REALLY odd. Adding "-listparam" to the end of the command shows that the parameter is being picked up:
/opt/pentaho/design-tools/pdi-ee-4.0.0-GA/kitchen.sh -norep -file=TestFile.kjb -level=Detailed -param:ZipFileName=ker.zip -listparam
INFO 25-06 13:44:55,154 - Using "/tmp/vfs_cache" as temporary files store.
INFO 25-06 13:44:55,500 - Kitchen - Kitchen
Parameter: ZipFileName=ker.zip, default=NONE : Full path name and file name of zip archive
The exact same command line without the "-listparam" still returns that it has no value in the variable.
Are we accessing the parameter value within the job in the wrong way?
Filing a support case for this one. Will post any resolution. (Case 00011014)
Last edited by khelms; 06-25-2010 at 04:18 PM.
The parameter on command line work in KEttle version 3.2.3.
Check if you have this:
1) Append
"-param:PARAM_NAME_1=PARAM_VALUE_1 -param:PARAM_NAME_2=PARAM_VALUE_2"
at end of kitchen command ?
2) That params are included in the job properties with right click + properties on the job canvas.
Dont work with
"-param:start_date=20100606"
Posted as case 4219:
http://jira.pentaho.com/browse/PDI-4219