This is an error very annoying with talend and in the most case, you have too wait a long times to see the error message and you don't know which column is responsible of the error. A simple way to avoid this error is to check the schema compliance with a tSchemaComplianceCheck.
It doesn't solve the problem but it permits to filter incorrect results and to know the reason of the error with the tLogRow component (REJECT_SCHEMA_COMPLIANCE) :
.---------+---------+-------+----+-----+-----+-----+----+---------+------------.
| REJECT_SCHEMA_COMPLIANCE |
|=--------+---------+-------+----+-----+-----+-----+----+---------+-----------=|
|JSON_DATE|JSON_RNSR|journal|type|orcId|idHal|idRef|code|errorCode|errorMessage|
|=--------+---------+-------+----+-----+-----+-----+----+---------+-----------=|
'---------+---------+-------+----+-----+-----+-----+----+---------+------------'
Now, in my case, I can insert in database only good results and filter bad results.
No comments:
Post a Comment