In one of the job, I want to capture the reject reason, why record got rejected in tMap. I am getting the rejected record, but want to capture the reason(error msg) why record got rejected. Is there any way to capture the reason in tMap?
Talend community celebrity @rhall_2_0 wrote a guide for this:
Hi, Thanks for your reply.
But that what I am not looking for.
My question is,
Suppose, for example, you have two files and you joined in tMap, now suppose, there are some records which are not joined, those records we can capture by setting "Catch lookup Inner join reject" to true. Now if you have 4-5 lookup in your tMap, and you set true for "Catch lookup Inner join reject", you will get the rejected records but you will not get the reason, why those rejects happening. what is the reason joining is not happening. From which lookup, record not matched and it comes to reject port.
Suppose, flow-1 is main flow, 2-4 are lookup flow.
when you joined, one record from flow-1 is not present in lookup-2 and it comes to reject port. Now record comes to reject port as value is not present in flow-2(lookup2) and same way for other flow.
so I need to capture the reason of reject., How we can do here in Talend.
@TRF thanks for your reply. But if I want to capture the message or some custom message, how this can be achieve for more than one join. Mesage for each record which fails in inner join.
There is also "ErrorReject" in tMap.This row link connects a tMap component to an output component. This link is enabled when you clear the Die on error check box in the tMap editor and it gathers data that could not be processed (wrong type, undefined null value, unparseable dates, etc.).