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

Dimension lookup/update creating multiple rows in DB when only 1 should be created when using 'Alternative Start Date'

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Severity: High
    • Resolution: Fixed
    • Affects Version/s: 4.0.0 GA
    • Component/s: None
    • Labels:
      None
    • 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

      Hi,

      Take a look at the attached ktr transformation and csv input file.

      The transformation should update a table in the database with new key pairs (2 keys need to match).

      If the target table is empty, the step inserts a row. However, in the same transformation run if your incoming resultset has multiple versions of the same pair of keys, each row will be written to the db. In this example, 84 rows are written where only 1 should.

      Initially thought this was a caching issue or commit issue. So tested the following scenarios:

      1. Commit = 100, Cache = 5000
      2. Commit = 1, Cache = 5000
      3. Commit = 1 Cache = 1
      4. Commit = 1 cache = disabled (or -1)

      All of the above experience the same behavior. This makes usages of the step limited to only a single key.

        Attachments

          Activity

            People

            Assignee:
            sflatley Sean Flatley (Inactive)
            Reporter:
            anthonycarter Anthony Carter (Inactive)
            Votes:
            1 Vote for this issue
            Watchers:
            1 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: