title: Pentaho Dimension Lookup/Update deadlock error
body: <p>I have a Dimension Lookup/update step, and I am trying to update a table with data from JSON files, but it is failing with the following error:</p>
  <pre><code>2021/08/03 12:51:58 - dlu-insrting_in_table.0 - ERROR (version 9.1.0.0-324, build 9.1.0.0-324 from 2020-09-07 05.09.05 by buildguy) : Because of an error this step can't continue: 
  2021/08/03 12:51:58 - dlu-insrting_in_table.0 - Couldn't get row from result set
  2021/08/03 12:51:58 - dlu-insrting_in_table.0 - Transaction (Process ID 78) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.
  </code></pre>
  <p>This is the configuration of the Dimension Lookup/update step.
  <a href="https://i.stack.imgur.com/XUKd2.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/XUKd2.png" alt="enter image description here" /></a></p>
  <p>and this is part of the transformation</p>
  <p><a href="https://i.stack.imgur.com/HimGt.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/HimGt.png" alt="enter image description here" /></a></p>
  <p>If I use only one copy to start the step, it works everything ok, but if I put more than one it gives me the mentioned error. The thing is that the error seems to be casual, sometime crashes after inserting two rows, other times it inserts everything without giving the error.</p>
  <p>Searching the documentation and in interned didn't help much, I was not able to fix it. I read that could be a insertion order problem or a primary key related problem, but the data is fine (the keys are unique) and the configuration of the step seems ok. What I noticed is that does not insert the Technical key in order, I think is because it depends on the process that finishes first, but I don't find a way to force it (assuming this is the problem).</p>
  <p>Does anyone know which is the problem here, and how could I fix it? Thank you.</p>