tFileInputDelimited Rejects

[Anonymous]

Hi Folks,

I'm trying to get to grips with the reason that rows are being rejected by a tFileInputDelimited component. According to the errorMessage column it's rejecting email addresses (schema: String (255) or String (100)). The addresses are quite short - average 20 characters - so I don't think it's rejecting them on length.

The thing that's really confusing me, though, is if I flow the rejected rows to a tFileOutputDelimited, and then pull them back in using a copy of the original tFileInputDelimited (same schema, with just the errorCode and errorMessage columns added), it accepts them without a problem:



Can anyone tell me why this might be? Does the Reject output strip out problematic data? It would seem odd if it did.

Cheers,

Matt

[TRF]

Hi,
If the schemas are identical, then the error is probably from the data.
Can you how us the schema for tFileInputDelimited_1 and tFileOutputDelimited_1 and a sample of rejected/unrejected rows?
Regards,
TRF

[Anonymous]

Thanks TRF. I'll add the schemas, but the data is something I can't share for legal reasons. I was wondering if there was a general principle which would explain why the rows in the Rejects output could be read successfully by another fFileInutDelimited with the same schema. I would expect such recycling to fail again, with the same error.


https://www.talendforge.org/forum/img/members/360155/tFileOutputDelimited_1_Schema.txt.txt
https://www.talendforge.org/forum/img/members/360155/tFileInputDelimited_1_Schema.txt.txt

[Anonymous]

I think I've got my answer - the Reject rows do indeed appear to strip out the rejected values. In a way this is actually quite useful behaviour.