Dates and epoch_millis as floats

[royrusso]

Attempting to migrate to 2.x, I've encountered a strange problem with range filters not able to match any of the mappings I try holding epoch_millis. Maybe related to #10971

Given a document with a time_stamp field in the mapping:

          "time_stamp": {
            "type": "date",
            "format": "epoch_millis"
          }

With some data:

station: "ASN00033312",
precip_tenths_mm: 2,
time_stamp: 1390712400000,
location: {
lat: -23.2233,
lon: 150.605
}

I would expect the following to match:

"query": {
    "filtered": {
      "filter": {
        "bool": {
          "must": [
            {
              "range": {
                "time_stamp": {
             "gte": 1390712400000,
             "format" : "epoch_millis"
                }
            }
            }
          ]
        }
      }
    }
  }

The above returns no document, even though there are thousands that should respond. Removing the format at query time, doesn't help. Mapping the time_stamp field as format "basic_date", as I had in 1.x, doesn't seem to return anything either.

Bug? Pebcak?

[royrusso]

I seem to have tracked it down... On indexing, my epoch timestamps are float format, ie. 1390798800000.0

ES is ignoring them, perhaps because of...

        "index.mapping.ignore_malformed" : true,
        "index.mapping.coerce" : true

I would've expected ES to "coerce" the float to an int and treat it as a epoch_millis, but instead it seems to be ignoring them altogether.

Not sure if this is the expected behaviour, so feel free to open/close the issue depending.

[clintongormley]

Hi @royrusso

Your diagnosis seems correct. I agree that we could coerce floats to longs for epoch_millis.

[tj]

👍 this is a pretty bad bug IMO, Go's json encoder may give you floats, and JSON numerical values by definition are floats, there's only the one type. Is there a workaround?