TL;DR; Valid: 2019-07-10T17:01:01.500Z Valid: 2019-07-10T17:01:01.50Z INVALID: 2019-07-10T17:01:01.5Z I want to know how to accept the invalid value as a valid value, since it is a valid date value. I'm trying to add a document that contains a date property, if this property has a time with a…

@Thiago_Coimbra_Lemos Hi just ran this all in 7.2.0 all ran fine... PUT my_index/_doc/1 { "value_at": "2019-07-10T17:01:01.500Z" } GET my_index { "my_index" : { "aliases" : { }, "mappings" : { "properties" : { "value_at" : { "type" : …

Invalid date because milliseconds does not contains trailing zeros

Elastic Stack Elasticsearch

dadoonet (David Pilato) July 13, 2019, 7:46pm 5

Could you try with 7.2 in case something has been fixed in the meantime?

1 Like

Topic		Replies	Views
Problem with far future millisecond values for Date type Elasticsearch	1	839	July 5, 2017
Transforms: date epoch_millis parsing errors Elasticsearch	3	716	July 3, 2020
Date Field with Millis stored as double leading to error Elasticsearch painless	5	766	August 6, 2021
Getting date parsing exception for milliseconds in a query Elasticsearch	3	2600	July 5, 2017
Indexing problem when missing milliseconds for strict_date_time field Elasticsearch	4	1821	July 5, 2017

Invalid date because milliseconds does not contains trailing zeros

Related topics