While this can be achieved in Talend by using OnSubJobError option with a falg value and looping mechanism, it is not the right approach to handle the issue. Following are the reasons for not doing this approach.
a) The situation proves that current architecture is not scalable beyond a point when traffic increases. Each transaction may result upto 10 times more traffic in intermediate layer
b) The current network capacity seems to be strained and it needs to be looked urgently
c) If you are using AWS or any cloud based solutions, make sure you are using right sized DB.
Warm Regards, Nikhil Thampi
Please appreciate our Talend community members by giving Kudos for sharing their time for your query. If your query is answered, please mark the topic as resolved 🙂
You can use tLoop to perform the required number of loops. In the condition of tLoop, you can add multiple conditions to verify whether the flag value is Y or N.
Now if the OnComponentError needs to be added to DB Output component and add a tJava to it. Inside tjava, assign the value of flag as Y. This means that only in the case of Component Error, it will go to tjava and change the value to Y.
Again, I would like to stress the fact that this is not an ideal approach for solution even though technically it will work.
Warm Regards, Nikhil Thampi
Please appreciate our Talend community members by giving Kudos for sharing their time for your query. If your query is answered, please mark the topic as resolved 🙂
