elasticsearch/x-pack/plugin/async-search
Nikita Glashenko 1db17ada95
Fix wrong error upper bound when performing incremental reductions (#43874)
When performing incremental reductions, 0 value of docCountError may mean that 
the error was not previously calculated, or that the error was indeed previously 
calculated and its value was 0. We end up rejecting true values set to 0 this 
way. This may lead to wrong upper bound of error in result. To fix it, this PR 
makes docCountError nullable. null values mean that error was not calculated 
yet.

Fixes #40005

Co-authored-by: Igor Motov <igor@motovs.org>
Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
2021-07-22 08:18:24 -10:00
..
qa Cleanup QA projects build scripts (#74428) 2021-06-23 11:35:47 +02:00
src Fix wrong error upper bound when performing incremental reductions (#43874) 2021-07-22 08:18:24 -10:00
build.gradle Remove internal build logic from public build tool plugins (#72470) 2021-05-06 14:02:35 +02:00