Jim Ferenczi c7a2c6d549

Handle IndexOrDocValuesQuery in composite aggregation (#35392) ...

The `composite` aggregation can optimize its execution when the query
is a `match_all` or a `range` over the field that is used in the first source
of the aggregation. However we only check for instances of `PointRangeQuery` whereas
the range query builder creates an  `IndexOrDocValuesQuery`. This means that
today the optimization does not apply to `range` query even if the code could handle it.
This change fixes this issue by extracting the index query inside `IndexOrDocValuesQuery`.

2018-11-15 17:52:06 +01:00

..

licenses

upgrade to lucene-8.0.0-snapshot-6d9c714052 (#35428)

2018-11-12 10:48:27 -06:00

src

Handle IndexOrDocValuesQuery in composite aggregation (#35392)

2018-11-15 17:52:06 +01:00

build.gradle

Upgrade to Joda 2.10.1 (#35410)

2018-11-12 10:02:41 +01:00