"-4" parsed as a date

[pcarrier]

$ curl -s -XPOST localhost:9200/test/1 \
       -d '{"foo":[{"bar": "-4"},{"bar": "::1"}]}' | \
       jq .
{
  "status": 400,
  "error": "MapperParsingException[Failed to parse [foo.bar]]; nested: MapperParsingException[failed to parse date field [::1], tried both date format [dateOptionalTime], and timestamp number]; nested: IllegalArgumentException[Invalid format: \"::1\"]; "
}

[s1monw]

this is above my head is '-4' a valid timestamp or not. It could be relative to 01.01.1970 in millis?

[s1monw]

hmm maybe I missunderstand are you complaining that -4 shoudl throw an exception as well or that -4 is interpreted as a date and you get a subsequent exception?

[pcarrier]

Hu no, I believe no human would ever say that this document looks like it contains any dates, so I'd expect not to run into any exceptions.

[kimchy]

Agreed on no humans, sadly, we are using computers :). Will work on fixing it, the string -4 should not be detected as a date, but as a string.

[pcarrier]

💻 doesn't have to overthrow 👪, but if it cannot find a year, month and day, I'd say it should not be guessing a timestamp.

[pcarrier]

If anybody arrives here by searching for the error, here's a workaround (disables date detection altogether on foo!):

% curl -XPUT localhost:9200/foo/_default_/_mapping -d '{"_default_":{"date_detection":0}}'