• Index
  •  » Talend Open Studio for Data Integration » Usage, Operation
  •  » Suggestion : before/after flow feature

#1 2007-03-09 14:45:25

fsoyer
Member
Registered: 2007-03-07
Posts: 53

Suggestion : before/after flow feature

I find a problem with a job : I want just one tMap with 3 MySQL output, but the first output must drop/create table (output columns may change in tMap, I don't want to have a tDBSQLRow in start to create table) while second and third must just insert into it when created.
So how can I control this "temporal" flows, when TOS execute the 3 output in parallel and I have no way to say it : start 2 and 3 after 1 ?
Yet another example : after the three insert output are finished, I want execute a TDBSQLRow (inserting an auto_increment column when all rows are inserted) : how be sure it start AFTER all inserts ?

Do you know SQLServer DTS ? Although it's M$ smile, it has some interesting features like a propertie for each flow to say : "before this one and/or this one, and/or after this other". It's really helping ! And you can really "draw" your process as you think it.

Well. Maybe complicated...

Last edited by fsoyer (2007-03-09 14:48:09)

Offline

#2 2007-03-12 15:01:54

fsoyer
Member
Registered: 2007-03-07
Posts: 53

Re: Suggestion : before/after flow feature

However, I reply to myself, we may split process in several subjobs and link them with before/after trigger. I can do that for my second example.
But is it working for all cases ? Like first example ?

Offline

  • Index
  •  » Talend Open Studio for Data Integration » Usage, Operation
  •  » Suggestion : before/after flow feature

Board footer

Powered by FluxBB