You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
if given some document date field that is a basic date, such as
{
"doc_field" : "20130425"
}
and _timestamp uses it as its path, it defaults to parsing the integer as ms rather than as the format
_timestamp{
"format":"yyyyMMdd",
"enabled":true
}
The text was updated successfully, but these errors were encountered:
spinscale
added a commit
to spinscale/elasticsearch
that referenced
this issue
May 22, 2013
The current implementation tries to parse every timestamp as a long first
and uses it as a unix timestamp.
This fails if the configured timestamp is like 'YYYYMMDD' and also
resembles a long by coincidence.
This PR tries to fix this issue by trying to parse it as a date first and
only it fails is tried to be parsed as a long from unix timestamp.
Possible problems:
* Performance: Reversing the order might make things slower.
* Wrong parsing: An additional check was added to make sure no negative
unix timestamps can be generated.
Closeselastic#2937
if given some document date field that is a basic date, such as
{
"doc_field" : "20130425"
}
and _timestamp uses it as its path, it defaults to parsing the integer as ms rather than as the format
_timestamp{
"format":"yyyyMMdd",
"enabled":true
}
The text was updated successfully, but these errors were encountered: