range query on dates can see small numbers of millis as a year

[nik9000]

If you write a date range query with numeric parameters we can interpret them as a year. Check it out:

curl -XDELETE -uelastic:password localhost:9200/test
curl -XPOST -HContent-Type:application/json -uelastic:password localhost:9200/test/_doc?refresh -d'{"d": "1970-01-01T00:00:01.010Z"}'
curl -XPOST -HContent-Type:application/json -uelastic:password localhost:9200/test/_doc?refresh -d'{"d": "1967-01-01T00:00:00.000Z"}'
curl -XPOST -HContent-Type:application/json -uelastic:password localhost:9200/test/_search?pretty -d'{
  "query": {
    "range": {
      "d": {
        "gt": 1000
      }
    }
  }
}'

The 1000 gets turned into a String internally and then we parse it as the year 1000.

[elasticmachine]

Pinging @elastic/es-search (:Search/Search)

[cbuescher]

I think we should force parsing with "epoch_millis" when the argument of to or from is a number. Working on a fix.

[nik9000]

I think maybe this an 8.0 breaking change kind of thing though.

[cbuescher]

For the record: numeric values smaller than 1000 are currently interpreted as is by "strict_date_optional_time||epoch_millis" (meaning they stay as they are), four digit numbers like 1000, 1555, 1968 are converte to milliseconds since epoch (negative and positive after 1970) and five digit numbers are again interpreted as is (e.g. 10000 stays like that, meaning 10000ms since 1970). This is truly odd and we certainly improve the situation by always parse ints with "epoch_millis" here.