I am a new TOS user and now in Dave's same boat. I have input data which has multiple contacts per account all in one row (not a great format, I know, but I inherited it.) My job is to split all the contact columns into separate streams with the same schema (easy enough with a tMap) and then re-merge the split data flows in the same way as a UNION operator would in SQL, so I have one nice data flow of contacts.
I do NOT think it's practical or desirable to have to write these streams out to file/database, then make new inputs and pump them all into the tUnite component.
WHY can't the tUnite component accept multiple inputs which happen to have been split off from a single input earlier upstream? This kind of operation would be really great to be able to accomplish simply. Are we all missing something, or has this still not been addressed?
Split the input based on 3 conditions and create 3 diff outputs. Try to join all the 3 outputs to a tUnite component. It wont allow us to join the 2nd and 3rd outputs.
Talend named a Leader.
Kickstart your first data integration and ETL projects.
Watch the recorded webinar!
Part 2 of a series on Context Variables
Learn how to do cool things with Context Variables
Find out how to migrate from one database to another using the Dynamic schema