Hitachi Vantara Pentaho Community Forums
Results 1 to 3 of 3

Thread: internal.job.filename.directory vs pentaho.solutionpath

  1. #1

    Default internal.job.filename.directory vs pentaho.solutionpath

    hello all,
    This is actually a problem from Pentaho 1.2/Kettle 2.5, but may still exist in future versions --

    When working with Spoon, you can use the 'Internal.Job.Filename.Directory' to keep things relative in the JOB (KJB) when defining the location of a TRANSFORMATION (KTR).

    However, when you deploy the job to Pentaho, Pentaho doesn't use the above, instead it uses 'pentaho.solutionpath'. from what I recall, Kettle 2.5 does not understand pentaho.solutionpath.

    Is this still a problem? If so:

    *Enhancement: Kettle to support 'pentaho.solutionpath' internal file name in a job when defining where KTR files exist relatively. Note that the filename is actually '%%pentaho.solutionpath%% in my old jobs.

    take care,
    -D

  2. #2
    Join Date
    May 2006
    Posts
    4,882

    Default

    I think it did support solutionpath if you made a small tweak in a file somewhere.

    Personally I don't like mixing stuff that much... that's just me

    Regards,
    Sven

  3. #3
    Join Date
    Nov 1999
    Posts
    9,729

    Default

    I remember messing with the Kettle Component to make those relative paths work. Would be interested to see a JIRA case if it still was a problem though.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
Privacy Policy | Legal Notices | Safe Harbor Privacy Policy

Copyright © 2005 - 2019 Hitachi Vantara Corporation. All Rights Reserved.