Skip to content

Commit 20f179f

Browse files
rand0m86pquentin
andcommitted
Add missing shard_min_doc_count to TermsAggregation (#2175)
Co-authored-by: Quentin Pradet <[email protected]> (cherry picked from commit 2bb4d0c)
1 parent 7b334ef commit 20f179f

File tree

3 files changed

+31
-8
lines changed

3 files changed

+31
-8
lines changed

output/schema/schema.json

Lines changed: 21 additions & 8 deletions
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.

output/typescript/types.ts

Lines changed: 1 addition & 0 deletions
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.

specification/_types/aggregations/bucket.ts

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -358,6 +358,15 @@ export class TermsAggregation extends BucketAggregationBase {
358358
value_type?: string
359359
order?: AggregateOrder
360360
script?: Script
361+
/**
362+
* Regulates the certainty a shard has if the term should actually be added to the candidate list or not with respect to the `min_doc_count`.
363+
* Terms will only be considered if their local shard frequency within the set is higher than the `shard_min_doc_count`.
364+
*/
365+
shard_min_doc_count?: long
366+
/**
367+
* The number of candidate terms produced by each shard.
368+
* By default, `shard_size` will be automatically estimated based on the number of shards and the `size` parameter.
369+
*/
361370
shard_size?: integer
362371
show_term_doc_count_error?: boolean
363372
size?: integer

0 commit comments

Comments
 (0)