Why doesn’t Informatica‘s joiner transformation support !=, >=, <= operators?
Why should they come up with a concept like lookup?
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Joiner transformation is used for vertical consolidation.
e.g
Using a join condition on order-tbl.item-id = item-tbl.item-id you could print a report like this
For vertical consolidation, I can’t think of a scenerio needing other conditions like !=, >=, <=.
With lookup transformation, some core ETL tasks are made easy like
identifying if the incoming record is a new record (primary key doesn’t exist) or an update to the existing record;
lookup a value e.g. lookup item-price from item-tbl to calculate order total.