Affects Version/s: 4.0.0 GA
Fix Version/s: 4.1.0 GA (Platform Release 3.7.0)
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.