Skip to content

[Docs] Add note on limitation for significant_text with nested objects #28052

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Jan 3, 2018
Merged

[Docs] Add note on limitation for significant_text with nested objects #28052

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
ef21345
[Docs] Add note on limitation for significant_text with nested objects
Jan 2, 2018
27bc716
Corrected typo
Jan 3, 2018
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions docs/reference/aggregations/bucket/significanttext-aggregation.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down