You are not logged in.
I've read in some post that it was not possible to have multiple links coming out from a tMap and link them to the same tUnite.
That's something I've already done with Datastage Server and that was the best solution of implementation.
The workarounds I've found :
- Using temp files or temp tables : that's less performance, and more objects to maintain.
- Concatenating the data in the tMap and using a tNormalizer to get the row : more complicate and harder to maintain
2 exemples of cases where I needed that kind of implementation :
- From lines of leaves containing a begin date and a end date, I need to get the number of days of each leave on each of the last 12 months.
To do that, I create 12 output links from the tMap. I put a condition on each of the link (if the leave has at least 1 day on that month), and I create a data containing the number of days of that leave on that month.
Then I put a tUnite to gather the links.
- When a line from a file for example can generate multiple lines in a table, depending on differents rules.
It would be handy to create a link for each rule, and then gather the links in a tUnite.
So is that kind of implementation could be considered in future release of TOS ?
Perhaps I just don't understand the TOS idiom, but it seems to me also that the simplest approach for many tasks would be the ability to split processing of a row input with multiple tmap outputs, manipulate the rows, then rejoin them, with a tUnite or something like it into a single row output stream again.
I spent a while researching and found the same workarounds as the recommended solution - temp files/tables or complicated custom logic. From the outside, it seems like a simple enough feature - take one row from any of several inputs and send it to a single output stream. Is there another simple, efficient way to accomplish this that I am missing?
Thanks, and I just need to say that despite my merge problem, I think Talend ROCKS!!! and I'm so glad I finally found it.