Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Courier Fetch Error ElasticsearchParseException[failed to parse date field [2014-12-04T19:03:41.413Z], tried both date format [yyyy-MM-dd HH:mm:ss.SSS zzz], and timestamp number]; nested: IllegalArgumentException[Invalid format: \"2014-12-04T19:03:41.413Z\" is malformed at \"T19:03:41.413Z\"]; }{[QZnhxUCvSuGirC6Ru88uqQ][clickstream] #2703

Closed
KaranMuthusamy opened this issue Jan 20, 2015 · 2 comments

Comments

@KaranMuthusamy
Copy link

I have Kibana4 beta2 with elasticsearch 1.4.1 and I got the following error when I try to Date Histogram on X axis also I have kibana advanced tab dataFormat as below
MMMM Do YYYY, HH:mm:ss.SSS,yyyy-MM-dd HH:mm:ss.SSS zzz,yyyyMMdd'T'HHmmss.SSSZ

Not sure why this is failing with this message below. Can same one help on this please.

example timestamp data:
2015-01-16T23:10:11.291Z - This is the format of Kibana timestamp as @timestamp and
"type" : "date", "format" : "dateOptionalTime"
AND
2015-01-04 01:21:54.749 GMT - This is format of date from doc on Elasticsearch and
"type" : "date", "format" : "yyyy-MM-dd HH:mm:ss.SSS zzz", it is manually defined on mapping.

Courier Fetch Error: unhandled error Error: Failed to get the doc: {"error":"SearchPhaseExecutionException[Failed to execute phase [query], all shards failed; shardFailures {[QZnhxUCvSuGirC6Ru88uqQ][clickstream][0]: ElasticsearchParseException[failed to parse date field [2014-12-04T19:03:41.413Z], tried both date format [yyyy-MM-dd HH:mm:ss.SSS zzz], and timestamp number]; nested: IllegalArgumentException[Invalid format: "2014-12-04T19:03:41.413Z" is malformed at "T19:03:41.413Z"]; }{[QZnhxUCvSuGirC6Ru88uqQ][clickstream][1]: ElasticsearchParseException[failed to parse date field [2014-12-04T19:03:41.413Z], tried both date format [yyyy-MM-dd HH:mm:ss.SSS zzz], and timestamp number]; nested: IllegalArgumentException[Invalid format: "2014-12-04T19:03:41.413Z" is malformed at "T19:03:41.413Z"]; }{[QZnhxUCvSuGirC6Ru88uqQ][clickstream][2]: ElasticsearchParseException[failed to parse date field [2014-12-04T19:03:41.413Z], tried both date format [yyyy-MM-dd HH:mm:ss.SSS zzz], and timestamp number]; nested: IllegalArgumentException[Invalid format: "2014-12-04T19:03:41.413Z" is malformed at "T19:03:41.413Z"]; }{[QZnhxUCvSuGirC6Ru88uqQ][clickstream][3]: ElasticsearchParseException[failed to parse date field [2014-12-04T19:03:41.413Z], tried both date format [yyyy-MM-dd HH:mm:ss.SSS zzz], and timestamp number]; nested: IllegalArgumentException[Invalid format: "2014-12-04T19:03:41.413Z" is malformed at "T19:03:41.413Z"]; }{[QZnhxUCvSuGirC6Ru88uqQ][clickstream][4]: ElasticsearchParseException[failed to parse date field [2014-12-04T19:03:41.413Z], tried both date format [yyyy-MM-dd HH:mm:ss.SSS zzz], and timestamp number]; nested: IllegalArgumentException[Invalid format: "2014-12-04T19:03:41.413Z" is malformed at "T19:03:41.413Z"]; }]"}

@KaranMuthusamy KaranMuthusamy changed the title Courier Fetch Error ElasticsearchParseException[failed to parse date field [2014-12-04T19:03:41.413Z], tried both date format [yyyy-MM-dd HH:mm:ss.SSS zzz], and timestamp number]; nested: IllegalArgumentException[Invalid format: \"2014-12-04T19:03:41.413Z\" is malformed at \"T19:03:41.413Z\"]; }{[QZnhxUCvSuGirC6Ru88uqQ][hookd-clickstream] Courier Fetch Error ElasticsearchParseException[failed to parse date field [2014-12-04T19:03:41.413Z], tried both date format [yyyy-MM-dd HH:mm:ss.SSS zzz], and timestamp number]; nested: IllegalArgumentException[Invalid format: \"2014-12-04T19:03:41.413Z\" is malformed at \"T19:03:41.413Z\"]; }{[QZnhxUCvSuGirC6Ru88uqQ][clickstream] Jan 20, 2015
@KaranMuthusamy
Copy link
Author

Hello, No one got similar error?

@rashidkpc
Copy link
Contributor

This is fixed in master: a5b8718

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants