honeymoose
/
OpenSearch
mirror of https://github.com/honeymoose/OpenSearch.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

[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
This commit is contained in:
Christoph Büscher 2018-01-03 16:28:23 +01:00 committed by GitHub
parent 5e3ba8a88d
commit 556d77c9ad
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 6 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
docs/reference/aggregations/bucket/significanttext-aggregation.asciidoc
View File

@ -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 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. 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 ===== 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 The counts of how many documents contain a term provided in results are based on summing the samples returned from each shard and