Run terms concurrently when cardinality is only lower than shard size #110369
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We currently run terms aggregations concurrently when cardinality is lower or equal to shard size. The issue is that when merging internal aggregations for cardinalities equal to the shard size, we don't know if we have truncate the list of terms, so an error is computed which is not expected.
This is happening here where the condition is
size < terms.getShardSize()
:elasticsearch/server/src/main/java/org/elasticsearch/search/aggregations/bucket/terms/AbstractInternalTerms.java
Line 118 in ecacb2e
To make sure the results are the same between concurrent and non-concurrent runs, we need to exclude situations where shard size == cardinality. This showed up in a random test.
fixes #105505