Kettle Internal.Job.Filename.Directory

Question

I am new to Pentaho Kettle and I wonder what Internal.Job.Filename.Directory ?

• Is this my SPoon.bat folder or the job / xfrm folder created?
• Is there a way to change it to point to a specific folder?

I am running SPoon.bat on Windows XP.

Answer 1

Internal.Job.Filename.Directory is an internal variable that is always available. It points to the directory in which the work is running.

You can find more information here .

Answer 2

Internal.Job.Filename.Directory installed only when you are not using the repository , and it is installed automatically. You cannot install it manually.

How not to use the repository?

When you start Spoon, you will get a dialog asking for a repository. Just close this cancellation dialog box and everything is fine!

It took me a while to find this: I was wondering why Internal.Job.Filename.Directory always empty. The repository was the cause.

Described here: http://jira.pentaho.com/browse/PDI-7434

Answer 3

Internal.Job.Filename.Directory is a cache environment variable that indicates the location of the job on disk.

Answer 4

To set the value of the Internal.Job.Filename.Directory variable, you need to run Job in this way:

String filename="path_filename"; KettleEnvironment.init(); JobMeta jobMeta = new JobMeta(filename, null); Job job = new Job(null, jobMeta); job.start(); job.waitUntilFinished();

Answer 5

this is a variable for your folder where the current job is located. if you are not using a repository, then you need to specify where the transforms are.

to make it more flexible, you can put jobs and conversions in the same folder and then you can use the Internal.Job.Filename.Directory file.

therefore, if your conversion is called: my.ktr then, to call it in the job, you can point to it {Internal.Job.Filename.Directory} /my.ktr

You can learn more about this in my course: pentaho tutorial

Answer 6

This variable is deprecated now in version 7 and later. You have to use Internal.Entry.Current.Directory, and this works regardless of the repository or not, so you can create more portable code.