Updated Date Range to Follow Documentation When Assuming Missing Values 8x

[john-wagster]

Based on a review of the documentation here: https://www.elastic.co/guide/en/elasticsearch/reference/current/query-dsl-range-query.html. Our behavior at query and index time for date range queries was inconsistent.

This would lead to what was discovered here: #111484 where an indexed date_range field like the one shown below would not be returned by the exact same query shown below.

I attempted to fix this by changing the query parser to use DateMathParser which rounds appropriately to what's documented above. This changes missing information in date time values to be inline with the documentation often by 1 millisecond (such as the time information in the below example).

A few concerns worth discussing with this are where this should land in terms of releases and impacts to customer who may have assumptions about how date range has been working up to this point. Opening this as a discussion with some caution around putting it in until we get appropriate feedback.

query example

PUT /test_index1?pretty
{
    "mappings" : {
        "properties" : {
            "opening_dates": {
              "type": "date_range",
              "format": "yyyy-MM-dd"
            }
        }
    }
}

PUT test_index1/_doc/7
{
    "opening_dates": [
    {
      "gte": "2014-09-18",
      "lte": "2016-12-18"
    }
  ]
}

GET test_index1/_search
{
  "explain": true, 
  "query": {
    "bool": {
      "must": [
        {
          "range": {
            "opening_dates": {
              "gte": "2014-09-18",
              "lte": "2016-12-18",
              "relation": "contains",
              "format": "yyyy-MM-dd"
            }
          }
        }
      ]
    }
  }
}

[github-actions]

Documentation preview:

• ✨ Changed pages