ANS-1075 · CSV IMPORT & DATA MIGRATION
Why Does tFileInputDelimited Skip Rows in Talend When Schema Types Are Incorrect?
Understand how incorrect data type definitions in a tFileInputDelimited component schema can lead to row skipping without halting job execution in Talend.
Short answer
When using a tFileInputDelimited component in Talend, specifying an incorrect data type in the schema for an output column will cause Talend to skip the affected rows. Although an error like 'For input String' may appear, the job connector will not stop, and subsequent OnSubjobOK triggers will remain valid.
Scenario
Users of Talend's tFileInputDelimited component may encounter situations where rows from an input CSV file are unexpectedly skipped during processing. This occurs despite the job appearing to continue execution, and subsequent subjobs triggered by OnSubjobOK conditions still running.
Solution
The primary cause for rows being skipped when using a tFileInputDelimited component in Talend is an incorrect data type specification within the component's schema. When the data type defined in the schema does not match the actual data type present in the input CSV file for a particular column, Talend will skip the row containing the mismatch. While Talend will log an error, often indicating 'For input String' if a non-string value is expected but a string is encountered, it will not halt the connector's execution. Consequently, any subsequent OnSubjobOK triggers will still be considered valid and will proceed. To resolve this, ensure that the data types defined in the tFileInputDelimited schema accurately reflect the data types of the corresponding columns in the input CSV file.
Expert NetSuite Support
Need help with this NetSuite issue?
CSV Import & Data Migration consulting and configuration support