Pages

Sunday, September 26, 2021

ERROR : value too long for the type ... character varying(255) : resolved !

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.

See more on  https://help.talend.com/r/en-US/7.2/validation/tschemacompliancecheck-tlogrow-tfileinputdelimited-tfileinputdelimited-setting-up-job-standard-component-enterprise-drop

No comments:

Post a Comment

Publication android : échec de la demande d'accès en production

  Après avoir attendu 14 jours avec 12 testeurs, j'ai pu enfin  faire une demande d'accès en production .C'est long et on se dit...