topic Re: date parse error and tSchemaComplianceCheck in Talend Studio

date parse error and tSchemaComplianceCheck

Anonymous — Sat, 16 Nov 2024 14:08:59 GMT

Hello!
As I've started the real work, more and more issues are coming up, sorry for bothering all the time
Well I have another issue when I enter a "error causing" - line into my test- input file: there is a Date in it which, for example is filled with "ffffff" instead of "24112008" for example.
I'm also using a tSchemaComplianceCheck - component which should help to write out a message into a special (delimited) file when the fields in a row don't have the correct format.
But now, the date parsing error is thrown earlier, in the tFileInputPositional - component and so there is a "parse error" - message written to system out/system error but as this wrong sentence never reaches the tSchemaComplianceCheck, the error is never written ino the delimited file.
Is there any other possibility to make this work?
Thank you in advance,
Stefan

Re: date parse error and tSchemaComplianceCheck

youssef2 — Mon, 24 Nov 2008 09:51:56 GMT

Hi,
Try defining your columns in tFileInputPositional as strings and then check what you want in tSchemaComplianceCheck with the option "use another schema for compliance check" checked.
Regards,
Youssef

Re: date parse error and tSchemaComplianceCheck

Anonymous — Mon, 22 Dec 2008 14:57:39 GMT

Hello!
The tComplianceCheck doesn't work here. I tried to use it with my date pattern, but the date will not be rejected eventhough the data doesn't match the pattern: there is a "unparseable date:" - message printed to the screen but the line is not written thorugh the "reject" connection.
Any ideas?
I have a poor data quality of the input files so I really need to write out the lines which are "bad".
Thank you.
Stefan

Re: date parse error and tSchemaComplianceCheck

Anonymous — Mon, 05 Jan 2009 02:36:21 GMT

How to catch the below error and display an error msg.
Message from server 'XYZ' (Msg 4002, Severity 14, State 1):
Login failed.
DB-Library error (Error 20014, Severity 2):
Login incorrect.

Re: date parse error and tSchemaComplianceCheck

Anonymous — Fri, 18 Dec 2009 23:17:10 GMT

Hi,
I am having the same issue as CrazyBird - The tSchemaComplianceCheck is not validating the date format even though one is defined.
Any ideas?
If this is a known error has it been fixed in the latest version?

Re: date parse error and tSchemaComplianceCheck

Anonymous — Mon, 21 Dec 2009 05:55:29 GMT

Hello

If this is a known error has it been fixed in the latest version?

It have been fixed in the latest version.
Best regards

shong

Re: date parse error and tSchemaComplianceCheck

Anonymous — Mon, 21 Dec 2009 17:19:01 GMT

Thanks Shong.

Re: date parse error and tSchemaComplianceCheck

_AnonymousUser — Mon, 19 Jul 2010 16:39:10 GMT

I am still facing this issue even after using TALEND V4.0.1.

Re: date parse error and tSchemaComplianceCheck

Anonymous — Tue, 23 Nov 2010 11:21:56 GMT

Hi,
i would like to know if this problem is fixed in the last version TIS v4.1.
Thanks.
Best regards

Re: date parse error and tSchemaComplianceCheck

_AnonymousUser — Wed, 13 Apr 2011 05:14:41 GMT

Hi i am trying the change the Date format for my output file.
My input .xls file has date in format dd/MM/YY but i want the output .csv file to have to have date as dd/MM/YYYY.

Re: date parse error and tSchemaComplianceCheck

alevy — Thu, 14 Apr 2011 01:59:55 GMT

Just change the date pattern of the output component.

Re: date parse error and tSchemaComplianceCheck

Anonymous — Wed, 27 May 2015 22:39:52 GMT

Does the tschemacompliancecheck only work with strings? I am having the same problem as CrazyBird in TOS V. 5.6.1
I have dates coming in via tfileinputdelimted and entering the tschemacompliancecheck which has the custom defined option selected. The "type" for the date column is set to date and the "date pattern" is "yyyy-MM-dd". However the bad dates are not getting rejected and I am getting NumberFormatException errors from the job.