Yes, using the Metadata Injector step makes the transformation dynamic. You can also parametrize the jobs/transformation to make it dynamic
The Shell script considers a return code of 0 to mean success, anything else is a failure. You can use hops to control the resulting flow.
The Call DB Procedure needs to be triggered. Use a Row generator step generating e.g. 1 empty row and link that with a hop to the Call DB Procedure step
The main difference between them is we can run a transformation using pan.sh while we can run a job using kitchen.sh
Yes, you can use the ‘Get System Info’ step in a transformation to get the Pentaho version. In the ‘Type’ column choose ‘Available Processors’.
Upon every upgrade, Pentaho enhances a step/remove a step/replace a step/add a configuration. Those steps which change from its default configuration is called depreciated steps
When you use them in your transformation it may fail once you upgrade your Pentaho. If not it slows your performance and you will lag behind the market standard if you do not update
In the step, you can specify the folder/directory location with a regex expression like ‘.*.txt’ in the wildcard tab. This ensures that you read all files present in a given location
To use the inbuild encryption method of Pentaho you can run the following command in case of linux “./encr.sh -kettle <password>” whereas in case of windows use “./encr.bat -kettle <password>”
Yes, you can use the ‘Dynamic SQL row’ step where you can pass the sql query dynamically from the previous step or using a parameter.