Skip to content

Commit 79b9fd3

Browse files
Correct rare-terms default precision in docs (#96887) (#96908)
1 parent e88d060 commit 79b9fd3

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

docs/reference/aggregations/bucket/rare-terms-aggregation.asciidoc

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -79,7 +79,7 @@ A `rare_terms` aggregation looks like this in isolation:
7979
|`field` |The field we wish to find rare terms in |Required |
8080
|`max_doc_count` |The maximum number of documents a term should appear in. |Optional |`1`
8181
|`precision` |The precision of the internal CuckooFilters. Smaller precision leads to
82-
better approximation, but higher memory usage. Cannot be smaller than `0.00001` |Optional |`0.01`
82+
better approximation, but higher memory usage. Cannot be smaller than `0.00001` |Optional |`0.001`
8383
|`include` |Terms that should be included in the aggregation|Optional |
8484
|`exclude` |Terms that should be excluded from the aggregation|Optional |
8585
|`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
352352
in `depth_first` mode. This will throw an exception since RareTerms is unable to process `depth_first`.
353353

354354
As a concrete example, if `rare_terms` aggregation is the child of a `nested` aggregation, and one of the child aggregations of `rare_terms`
355-
needs document scores (like a `top_hits` aggregation), this will throw an exception.
355+
needs document scores (like a `top_hits` aggregation), this will throw an exception.

0 commit comments

Comments
 (0)