ERROR_MESSAGE is not always the same

Four Stars

ERROR_MESSAGE is not always the same

We loose information on ERROR_MESSAGE depending if i use a component or not.

 

The first test was made without using a component.

 

The Test Job...

Test-01-Job.jpg

 

The XML file with an error on line 1 (the second node) :

according to the schema, the value "B" must be an INTEGER.

Test-01-XML2.jpg


The console with the error message : "For input string: "B"Test-01-Console-Error2.jpg

 

In the second test, we added a "Reject" to a tLogRow.

The console log show a better ERROR_MESSAGE in the sense that we now have the line number that caused the error.

The Test Job modified with a "Reject" to a tLogRow

Test-02-Job.jpg

 

The console is now displaying the error with a very usefull addtionnal information " - Line: 1
Test-02-Console-Error.jpg

In conclusion, without the "Reject" we have a poor ERROR MESSAGE and when i use a "Reject" to a tLogRow we have only an information message.

 

Question : what is the path to have a verbose and undenatured log message ?

 

Five Stars

Re: ERROR_MESSAGE is not always the same

Hi DREYNAUD!

 

Instead of tlog, if your goal is achieve more detailed info about your possible errors at the subjob, I highly recommend you use the tLogCatcher component. With it you can extract all detailed information about your job errors.

 

Pls, give me some Kudos if my response help you Smiley Very Happy

Thanks for your time and attention.

 

PataToT

 

 

 

 

Four Stars

Re: ERROR_MESSAGE is not always the same

Thank you for your response.

I have tried using a tLogCatcher. Unfortunately the error message remains poor and did not contains the line number causing the error.

 

With_tLogCatcher.PNG

 

 

Forteen Stars

Re: ERROR_MESSAGE is not always the same

@DREYNAUD ,what was the column data type for debut? i believe it you might have specified number or Integer.since you are getting sting kind of data for the second record,if you change the date type to sting ,you should not get this error.

Manohar B
Don't forget to give kudos/accept the solution when a replay is helpful.
Highlighted
Four Stars

Re: ERROR_MESSAGE is not always the same

I deliberately put "B" in to cause a schema error (an integer is expected in the schema) and see the behavior of the logs.

15TH OCTOBER, COUNTY HALL, LONDON

Join us at the Community Lounge.

Register Now

2019 GARNER MAGIC QUADRANT FOR DATA INTEGRATION TOOL

Talend named a Leader.

Get your copy

OPEN STUDIO FOR DATA INTEGRATION

Kickstart your first data integration and ETL projects.

Download now

What’s New for Talend Summer ’19

Watch the recorded webinar!

Watch Now

Best Practices for Using Context Variables with Talend – Part 4

Pick up some tips and tricks with Context Variables

Blog

How Media Organizations Achieved Success with Data Integration

Learn how media organizations have achieved success with Data Integration

Read

Why Companies Move to the Cloud: 7 Success Stories

Learn how and why companies are moving to the Cloud

Read Now