From 2a43f18b950d0e715379277952edb9ba4471d0b1 Mon Sep 17 00:00:00 2001 From: Craig Taverner Date: Sun, 18 Jun 2023 21:51:31 +0200 Subject: [PATCH] Correct rare-terms default precision in docs (#96887) --- .../aggregations/bucket/rare-terms-aggregation.asciidoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/reference/aggregations/bucket/rare-terms-aggregation.asciidoc b/docs/reference/aggregations/bucket/rare-terms-aggregation.asciidoc index 525672be11d1f..d02b75db96af0 100644 --- a/docs/reference/aggregations/bucket/rare-terms-aggregation.asciidoc +++ b/docs/reference/aggregations/bucket/rare-terms-aggregation.asciidoc @@ -79,7 +79,7 @@ A `rare_terms` aggregation looks like this in isolation: |`field` |The field we wish to find rare terms in |Required | |`max_doc_count` |The maximum number of documents a term should appear in. |Optional |`1` |`precision` |The precision of the internal CuckooFilters. Smaller precision leads to -better approximation, but higher memory usage. Cannot be smaller than `0.00001` |Optional |`0.01` +better approximation, but higher memory usage. Cannot be smaller than `0.00001` |Optional |`0.001` |`include` |Terms that should be included in the aggregation|Optional | |`exclude` |Terms that should be excluded from the aggregation|Optional | |`missing` |The value that should be used if a document does not have the field being aggregated|Optional | @@ -352,4 +352,4 @@ that require `depth_first`. In particular, scoring sub-aggregations that are ins in `depth_first` mode. This will throw an exception since RareTerms is unable to process `depth_first`. As a concrete example, if `rare_terms` aggregation is the child of a `nested` aggregation, and one of the child aggregations of `rare_terms` -needs document scores (like a `top_hits` aggregation), this will throw an exception. \ No newline at end of file +needs document scores (like a `top_hits` aggregation), this will throw an exception.