One Star

tFileInputDelimited and "Unparseable date"

Hello.
I'm reading in rows from CSV files using tFileInputDelimited.
The data has values that are unparseable as dates so
apparently Talend just ignores those rows and starts with
the next one. Can this behaviour be changed, like for example
insert a null where unparseable? Or is it just load in as string
and use tMap for the job?
JB
2 REPLIES
Moderator

Re: tFileInputDelimited and "Unparseable date"

Hi,
What's your input data? How did you set your column schema structure? Could you please upload your job design screenshots into forum?
Best regards
Sabrina
--
Don't forget to give kudos when a reply is helpful and click Accept the solution when you think you're good with it.
One Star

Re: tFileInputDelimited and "Unparseable date"

What's your input data? How did you set your column schema structure? Could you please upload your job design screenshots into forum?

Hello Sabrina.
Job design:
tFileInputDelimited_1 --row1(Main)-> tMap_1 --out1(Main)-> tLogRow_1

Column schema structure for the tFileInputDelimited_1 is
from Repository, DELIM: test - metadata regarding the
problematic column is:

Column            Type  Date pattern  Length
Date_column_name Date "dd.MM.yyyy" 13

Data is:

String_column1|Date_column|String_column2
foo|21.08.2014|bar
foo|VALUE|bar

where "VALUE" is source system produced string "VALUE"
which is causing the unparseable error. The lines with
unparseable dates are ignored.
The question is can I change the behaviour of tFileInputDelimited
to not ignore the bad values but instead insert a null or
empty instead that I could catch later in tMap?
Sorry for not being clear enough in the original post.
JB