GitHub user swaroopchenchu added a comment to the discussion: What is best approach instead of DB lookup?
thanks for the suggestion 1. The limitation with chained Input Table transforms is that the second Input Table does not forward fields produced by the first Input Table. Although those fields can be accessed inside the second transform through the ‘?’ parameters, they are not carried forward to the rest of the pipeline. proof: left pane with first input table output fields right pane with second input table output fields <img width="827" height="414" alt="image" src="https://github.com/user-attachments/assets/5e0fef9e-6fe6-4b9d-ba04-2b1cfb0b07bb"; /> 2. As far as merge join(LEFT OUTER JOIN), defeats my purpose Because if second entity have multiple records, we don't want to place new record in first entity of same data. Imagine first entity have one record and second entity have two records for that Id. we have to place once in first Entity, with the same Id we generated we have to place two records in second entity. <img width="935" height="433" alt="image" src="https://github.com/user-attachments/assets/ec623791-69b6-4e4a-905e-7a7a8ec7ff4f"; /> Database joins allows us to do this, but need better approach to run it in migration window. Thanks Again GitHub link: https://github.com/apache/hop/discussions/6136#discussioncomment-15199153 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
