i´m using a tFileInputDelimited to read a csv file, which is connected to a tMap. The tMap then is connected to a tSchemaComplianceCheck, which then is connected to a tMSSqlOutput.
Inside the tMap i use the Expressioneditor for date fields, as we are struggling with invalid date data.
TalendDate.isDate(StringHandling.TRIM(row1.RBKP_BLDAT), "dd.MM.yyyy") ? TalendDate.parseDate("dd.MM.yyyy", StringHandling.TRIM(row1.RBKP_BLDAT)) : null
So the input stream should be checked by the TalendDate.isDate function. If the date is a valid date then it should be passed to the TalendDate.parseDate function for the output stream, if it´s not a valid date it should simply pass NULL to the output stream.
The invalid date is:
So what i am asking is: why does the TalendDate.isDate function return true instead of false for that date, and therefor an invaled date for the output stream?
I´m getting a
Exception in component tMSSqlOutput_1 java.sql.SQLException: Only dates between January 1, 1753 and December 31, 9999 are accepted.
Or how could i make sure always pass valid dates to the tMSSqlOutput stream?
Thanks in advance.
@bey0nd,in a tMap of under Activate /unactivate expression filter specify the below way and let me know.
If I'm understanding your explanation correctly, the problem is that 17.02.0118 is a valid date (17th February 118), so Talend is happy, however, SQL Server doesn't like a date in the year 118, hence its message about the year must be between 1753 and 9999.
You probably need some kind of data quality check to ensure that dates are within a sensible range.
Talend named a Leader.
Kickstart your first data integration and ETL projects.
Learn how to do cool things with Context Variables
Find out how to migrate from one database to another using the Dynamic schema
Pick up some tips and tricks with Context Variables