topic Re: Error Handling in Talend in Talend Studio

Error Handling in Talend

Anonymous — Sat, 16 Nov 2024 12:21:46 GMT

Hello Folks,
I am very new to talend development. I have very good experience in SSIS (SQL Server ETL tool). In SSIS, while processing the records, if any particular component fails due to an error in data like data conversion error or truncation of data or any other error, SSIS has the flexibility to redirect the rows that failed to process into a file or table by defining the on error component in the package.Is it possible to the similar workflow in Talend? I have looked at tconverttype which only handles the errors related to data conversion. Is there any component or solution to design a generic solution to redirect the rows failed to process to a table or file using Talend? I really appreciate all your inputs.
Thanks in advance!!!

Re: Error Handling in Talend

Anonymous — Mon, 20 Feb 2012 10:59:18 GMT

Hi,
Most components in Talend support the Reject row (make sure you disable the Die on Error option).
Usually I prefer to have a tMap component which receives the Reject row and maps some columns to an output (most of the time including the complete input row). This output is then sent to a Subjob that does generic error logging, like saving all data to a database table.
Hope this helps.
Regards,
Arno

Re: Error Handling in Talend

Anonymous — Tue, 21 Feb 2012 06:29:54 GMT

Thanks Arno for your quick reply. I have already enabled the reject row setting on the tmap but its not working. I have added a screenshot related to it. I am not sure whether i have configured it correctly or not.How to create a subjob that gets executed when the error occurs?
Thanks!!

Re: Error Handling in Talend

Anonymous — Wed, 22 Feb 2012 10:02:06 GMT

Can someone help me regarding this?
Thanks in advance!!!

Re: Error Handling in Talend

Anonymous — Wed, 22 Feb 2012 12:11:00 GMT

Hi,
> How to create a subjob that gets executed when the error occurs?
well, as you've said, you can create a subjob that executes in case of an error (I don't know if it will solve your problem)
component -> another component
|
| onError
\/
error subjob

Cheers
Gabriel

Re: Error Handling in Talend

Anonymous — Thu, 23 Feb 2012 10:38:20 GMT

I have the same issue, only the setup is a bit different... I have a tFileInputExcel that has a schema, when someone accidentally puts the wrong file, an error will show up ...

Exception in component tFileInputExcel_1
org.apache.poi.openxml4j.exceptions.InvalidOperationException: Can't open the specified file:

I want to catch this error, remove it from the console and dump it to a log file, so in the console everything will look like a normal run. tLogCatcher does the dumping but how do i suppress the error from the console?

Re: Error Handling in Talend

Anonymous — Thu, 23 Feb 2012 11:32:51 GMT

I want to catch this error, remove it from the console and dump it to a log file, so in the console everything will look like a normal run. tLogCatcher does the dumping but how do i suppress the error from the console?

You need to move this processing into a child job.
In child job, check the option 'die on error' on tFileInputExcel and use tLogCatcher to dump it to a log file.
In parent job, use a tRunJob to call the child job and uncheck the option 'die on error' on tRunJob. You will not see the error message on the console when running the parent job.
Best regards
Shong

Re: Error Handling in Talend

Anonymous — Thu, 23 Feb 2012 12:41:57 GMT

nope... I still get the error in the console when running the parent...

 connecting to socket on port 3609
 connected
Exception in component tFileInputExcel_1
org.apache.poi.openxml4j.exceptions.InvalidOperationException: Can't open the specified file:

Re: Error Handling in Talend

Anonymous — Fri, 24 Feb 2012 12:26:51 GMT

nope... I still get the error in the console when running the parent...

 connecting to socket on port 3609
 connected
Exception in component tFileInputExcel_1
org.apache.poi.openxml4j.exceptions.InvalidOperationException: Can't open the specified file:

Hi
Yes, you are right. The exception messages are still printed on the console even though it is called from a parent job.
Maybe the tSystem component could fix you need, export the job script and use a tSystem component to execute the job script in another job. On tSystem, select 'normal' in both Standard Output and Error Output list.

Best regards
Shong