From 556d77c9ad4c8e07a43f03218545b3f1ce2afa2a Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Christoph=20B=C3=BCscher?= Date: Wed, 3 Jan 2018 16:28:23 +0100 Subject: [PATCH] [Docs] Add note on limitation for significant_text with nested objects (#28052) Add section to `significant_text` documentation mentioning that it currently does not support use on nested objects. Relates to #28050 --- .../bucket/significanttext-aggregation.asciidoc | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/docs/reference/aggregations/bucket/significanttext-aggregation.asciidoc b/docs/reference/aggregations/bucket/significanttext-aggregation.asciidoc index cf282bb7fce..11dd0ea7b99 100644 --- a/docs/reference/aggregations/bucket/significanttext-aggregation.asciidoc +++ b/docs/reference/aggregations/bucket/significanttext-aggregation.asciidoc @@ -334,6 +334,12 @@ Clients can always take the heavily-trimmed set of results from a `significant_t make a subsequent follow-up query using a `terms` aggregation with an `include` clause and child aggregations to perform further analysis of selected keywords in a more efficient fashion. +===== No support for nested objects + +The significant_text aggregation currently also cannot be used with text fields in +nested objects, because it works with the document JSON source. This makes this +feature inefficient when matching nested docs from stored JSON given a matching +Lucene docID. ===== Approximate counts The counts of how many documents contain a term provided in results are based on summing the samples returned from each shard and