From 8e63ce00f0f1f64d835b1d1ea52f15184bbda6e4 Mon Sep 17 00:00:00 2001 From: Martijn van Groningen Date: Tue, 19 Apr 2016 11:49:51 +0200 Subject: [PATCH] docs: removed confusing statement. --- .../aggregations/metrics/tophits-aggregation.asciidoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/reference/aggregations/metrics/tophits-aggregation.asciidoc b/docs/reference/aggregations/metrics/tophits-aggregation.asciidoc index afbb40b5b1a..1dd1524a58e 100644 --- a/docs/reference/aggregations/metrics/tophits-aggregation.asciidoc +++ b/docs/reference/aggregations/metrics/tophits-aggregation.asciidoc @@ -192,8 +192,8 @@ relevancy order of the most relevant document in a bucket. -------------------------------------------------- At the moment the `max` (or `min`) aggregator is needed to make sure the buckets from the `terms` aggregator are -ordered according to the score of the most relevant webpage per domain. The `top_hits` aggregator isn't a metric aggregator -and therefore can't be used in the `order` option of the `terms` aggregator. +ordered according to the score of the most relevant webpage per domain. Unfortunately the `top_hits` aggregator +can't be used in the `order` option of the `terms` aggregator yet. ==== top_hits support in a nested or reverse_nested aggregator