Hello.
It seems that date_formats doesn't work as expected.
Everything is described in following gist:
Am I doing something wrong?
Regards
Wojciech Durczyński
Hello.
It seems that date_formats doesn't work as expected.
Everything is described in following gist:
Am I doing something wrong?
Regards
Wojciech Durczyński
Hello
Have you ever checked the right formats expect by Joda date parser?
http://joda-time.sourceforge.net/api-release/org/joda/time/format/DateTimeFormat.html
2012/2/10 Wojciech Durczyński wojciech.durczynski@comarch.com
Hello.
It seems that date_formats doesn't work as expected.
Everything is described in following gist:
Elastic Search date_format problem · GitHub
Am I doing something wrong?Regards
Wojciech Durczyński
--
's
Shairon Toledo
http://www.google.com/profiles/shairon.toledo
Of course.
And I'd like to use "basic_date_time" format. It looks like
this: yyyyMMdd’T’HHmmss.SSSZ
And I configured "basic_date_time" as a default format, what doesn't work.
On Fri, 2012-02-10 at 02:16 -0800, Wojciech DurczyÅski wrote:
Hello.
It seems that date_formats doesn't work as expected.
Everything is described in following gist:
Elastic Search date_format problem · GitHub
I can confirm that this looks broken. Please open an issue
demonstrating the problem (and remove the dynamic mapping, it is still
broken without that)
ta
clint
Issue created:
This happens because there is a basic check to see if something is a date by looking for :, -, and / in the string before trying to parse it. Otherwise, is 20120101 a numeric number or a date? I guess we can improve that to also look for T, and if its there, try and parse.
On Friday, February 10, 2012 at 3:13 PM, Wojciech Durczyński wrote:
Issue created:
date_formats doesn't work · Issue #1690 · elastic/elasticsearch · GitHub
© 2020. All Rights Reserved - Elasticsearch
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant logo are trademarks of the Apache Software Foundation in the United States and/or other countries.