Uploaded image for project: 'Pentaho Data Integration - Kettle'
  1. Pentaho Data Integration - Kettle
  2. PDI-13339

${Internal.Transformation.Filename.Directory} problematic in JCR

    XMLWordPrintable

    Details

    • Story Points:
      0
    • Notice:
      When an issue is open, the "Fix Version/s" field conveys a target, not necessarily a commitment. When an issue is closed, the "Fix Version/s" field conveys the version that the issue was fixed in.
    • Operating System/s:
      Ubuntu 12.x (64-bit)

      Description

      CE:

      In CE ktr's are not first class citizens, we can however use CDA to load them as a datasource, using ${Internal.Transformation.Filename.Directory} poses a problem though, as it will always point to file system.
      Relates to http://jira.pentaho.com/browse/CDA-91.
      The workaround for this one has been to replicate the jcr path in the file system, and have relevant resources there.
      ex. a ktr loaded by cda running in the jcr:
      /home/admin
      would have its relevant resources in the filesystem:
      .../bi-server/pentaho-solutions/home/admin/

      EE:

      In EE ktr's are first class citizens, running the attached sample.ktr will write to log ${Internal.Transformation.Filename.Directory}, which outputs this:

      "path = "

      It should also write to log the filenames in the folder ${Internal.Transformation.Filename.Directory}, it doesn't

      So is ${Internal.Transformation.Filename.Directory} an empty string?
      This would mean ${Internal.Transformation.Filename.Directory} is currently unusable in the jcr.

      Note:
      This seems to relate to KettleVFS being used, which only returns files from the file system.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned
              Reporter:
              jvelasques Joao Velasques (Inactive)
              Votes:
              1 Vote for this issue
              Watchers:
              4 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: