topic Re: tDie - Best practice in Talend Studio

tDie - Best practice

Anonymous — Wed, 12 Dec 2018 07:40:48 GMT

Hi there,

I have a question about how to optimize the use of tDie in my project.

Is that a good thing to use a subjob and put the tDie inside ?

I see some avantages :

- you can format a message using context var, and so you have the same message in all you call to tDie ;

- you can change easily the priority for all your tDie (if you have a specific priority, then you can call directly your tDie) ;

- You can set the Error code you want in variable context ;

- And you can also do what you want when a tDie is called. For instance, you can send an email to inform about the fatal / error.

- You can easily change the option "Leave the JVM immediatly"

What do you think about it ?

Is that better to use directly the tDie in your jobs, or use them in a specific job called by the others ?

And same question for the tWarn.

Thank for your reply !

Re: tDie - Best practice

Anonymous — Wed, 12 Dec 2018 09:55:07 GMT

Hi,

The best practice will be to use tDie using onSubJobError in same job. Please refer the below link containing Talend Best Practices for details.

https://www.talend.com/blog/2015/12/07/talend-job-design-patterns-and-best-practices/

But please note that different customers configure the tDie according to specific use case. If you have a specific use case where you would like to capture more details, you can go for a separate sub job also. But in my view, its an additional overhead.

If the answer has helped you, could you please mark the topic as resolved? Kudos are also welcome 🙂

Warm Regards,

Nikhil Thampi

Re: tDie - Best practice

Anonymous — Fri, 14 Dec 2018 13:51:28 GMT

Thank you for your answer Nikhil, I have read the 4 parts of these best practices but I was wondering if it was better or not