topic Re: Unparseable date error in Talend Studio

Unparseable date error

_AnonymousUser — Sat, 16 Nov 2024 14:15:07 GMT

I'm parsing through a CSV file and mapping it over to a MySQL database connection and when I run the job, I get an unparseable date error for every row (except for one). I've provided a couple of the error lines below, along with the date format that I've specified in the metadata. Anyone have any ideas as to what could cause this?
Unparseable date: "2006-11-03 15:11:34"
Unparseable date: "2006-11-06 10:35:15"
Unparseable date: "2006-11-08 13:15:17"
Unparseable date: "2006-11-10 13:51:34"
...
Date format: "yyyy-MM-dd HH:mm:ss"
Thanks.

Re: Unparseable date error

Anonymous — Wed, 27 Aug 2008 02:45:45 GMT

Hello
Which version of TOS are you using?
I tested it on TOS3.0.0M2 and it works fine.(please see the screenshot)
Best regards
shong

Re: Unparseable date error

Anonymous — Tue, 04 Jun 2013 12:23:34 GMT

Hi Shong,
I am working on Talend 5.3.0.r101800
My dates are in format DD/MM/YY in csv and I want to convert it into MM/DD/YYYY.
I have tried many cobination but no luck.
Can you suggest here.

Re: Unparseable date error

Anonymous — Wed, 05 Jun 2013 04:25:41 GMT

Hi gopal_raturi,

My dates are in format DD/MM/YY in csv and I want to convert it into MM/DD/YYYY.

Could you please elaborate your case with an example with input and expected output values? "DDD" stands for Day in year(001-366). "dd" stands for Day in month(01-31). Could you confirm it? Thanks a lot.
Best regards
Sabrina

Re: Unparseable date error

Anonymous — Wed, 20 Nov 2013 03:03:08 GMT

Hi, I am having the same problem, I even change all the date types to string but still same problem. Can anyone help

Re: Unparseable date error

Anonymous — Wed, 20 Nov 2013 03:18:01 GMT

Hi adjrock,
Could you give us more information about your current situation. What's your input and expected result?
Best regards
Sabrina

Re: Unparseable date error

Anonymous — Tue, 26 Nov 2013 17:17:12 GMT

Hi, I'm also experiencing this error
Using tFileFetch --> tFileInputDelimited --> tMap --> MysqlOutput
When I do a debug run I see unexpected text date formats like, "Mon Nov 25 00:00:00 PST 2013"
Here is my console:

connecting to socket on port 3436
connected
connecting to socket on port 4932
connected
Status Line: HTTP/1.1 200 OK
*** Response Header ***
Cache-Control: no-cache
Content-Type: text/csv; charset=UTF-8
Content-Disposition: attachment; filename=query_response.csv
Vary: Accept-Encoding
Date: Tue, 26 Nov 2013 17:11:31 GMT
Server: Google Frontend
Alternate-Protocol: 443:quic
Transfer-Encoding: chunked
Unparseable date: "ga:date"

However, the actual data gets transferred fine into my MySQL table, the dates are ok... a bit odd
Please see screen captures for my configuration; if you need any other information let me know, thanks

Re: Unparseable date error

Anonymous — Tue, 26 Nov 2013 18:00:25 GMT

Hi ddctf
There is a value "ga:date" in the source file that is unparseable, if you check the 'die on error' option on tFileInputDelimited, the job will throw the exception and stop at this line.
Shong

Re: Unparseable date error

Anonymous — Tue, 26 Nov 2013 18:36:32 GMT

Resolved, thank You