GitHub user swaroopchenchu added a comment to the discussion: What is best approach instead of DB lookup?
Thanks bamaer and liosc Since i am picking only record from second entity, i went ahead with rank in query and that solved for one pipeline. but i have other pipeline where i do need all multiple records and then make it into list and then place at once so that primary key of first entity will go same as field in second Entity eg: A.ActivationId == B.Activation These entity have 133Million and 125 Million records. I think hop doesn't allow two Table input transform in one pipeline, if it had we could have query in second table input with ActivationId coming from first table Input transform. I was migrating these two entities separately, but source system primary key is of GUID(eg: 163D24B4-88FC-E811-9F80-000C2979F806) type, with guid we cant scale in destination system API performance is blown. Hence two entities have to be handled in single pipeline to place primary Key same in other field of second Entity. since these Entity's are huge. Any ideas to solve this? GitHub link: https://github.com/apache/hop/discussions/6136#discussioncomment-15180502 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
