Commits in child job

[Anonymous]

Hello,

I just encountered an issue with commits and child job, see my explanations below.

There i've made a job that transforms and moves some datas from two bases to two others. I end this job by commiting the four databases (actually 2 are enough i know).

After that, when i do a select count(*) , it returns me 5414 rows which is great.

Now i want to put these 4 commits inside another job in order to simplify my flows and because i may use them several times.

So i did that :

These 4 commits have been coppied from the first job and my connections are shared.

After that, when i do a select count(*), it returns me 0 rows which means nothing has been commited, right ?

What's the problem ?

Thanks

[Anonymous]

Hi,

     In your child jobs, you are providing new DB connection parameter and the commit components are using them for committing the values. This means the database is considering them as a new connection and they do not have any relationship with your previous DB connection.

Warm Regards,

Nikhil Thampi

[Anonymous]

Oh yes i see the problem ... so i guess there is no solution to do what i wish, right ? Sounds sad !

[Anonymous]

Finally, after thinking, I don't really understand why does it work like this ?! I'm using shared connections between my jobs (parents and childs) so every connection, every use in child job, should not be considered as a new one, right ? If it works like this, what's the point of shared connection ?

[Anonymous]

Hi,

     Could you please share the current component screen shots for the shared connection between parent and child jobs so that I will get more idea about your current use case?

     Could you please cross check your job component details with sample scenario given in help document below?

https://help.talend.com/reader/9q55KsfASqX0qY4GVhEDNQ/EBKmz8HbKw4uTMpBaHzz5Q

Warm Regards,

Nikhil Thampi

[Anonymous]

[Anonymous]

@shong - In the above scenario, the connection is happening through Maria DB database but the connection seems not working. 

Is there any limitation for this functionality to work only in classic MySQL DB alone? I was checking KB article on this item and I could see some errors are popping up for other DBs. Could you please advise on this?

https://community.talend.com/t5/Migration-Configuration-and/Sharing-a-database-connection-between-a-...

Warm Regards,

Nikhil Thampi

[Anonymous]

I tried to remove all connection db parameters and the job (and its child job) worked perfectly. I mean, no exception has been thrown... but my inserts have not been commited...

[Anonymous]

God, i guess i got it ! My bad ... i think it was all about successives tasks. I just connected my connection components with "onSubjobOk" and it seems to work pretty well now. If that patch is right... it was so obvious.

I'll tell you if something's still wrong of course.

Thanks again and again.

Guillaume

[Anonymous]

Hi GuilLaume
Yes, you should use OnsubjobOK to control the execution order of subjob, make sure the connection is created before it is commit.

Regards
Shong