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

FAQ attack: Multiple copies of a step need sometimes data movement copy instead of distribution

    XMLWordPrintable

    Details

    • 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.

      Description

      Example:
      While debugging a transformation I built, I found that my stream lookup, when set to have multiple copies was not finding matches for an incoming record that was there. I have 3 incoming records (all with the same incoming value). It found one match, but used the default value for the other two, even though they all had the same value. When I set the step back to one copy, it then found matches for all of them.

      Solution was to set the data movement from distribution to copy. This is by design.

      User was always under the impression that this was handled in the background when you created multiple copies. But this is not true for steps that act with info steps.

      Could be adressed by a BIG warning to the user.

        Attachments

          Activity

            People

            Assignee:
            Unassigned
            Reporter:
            jbleuel Jens Bleuel
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Dates

              Created:
              Updated: