Lucene total hit count is wrongly considered exact on timeout

Description

The problem is made visible by a fix for HSEARCH-4079. Before that fix, we used to take a specific path in test timeouts that resulted in the hit count being set to 0 and considered as a lower bound.

But in the general case, we won't take that path on timeouts, and the hit count will wrongly be considered as exact.

Activity

Show:
Fixed

Details

Assignee

Reporter

Components

Sprint

Fix versions

Priority

Created October 28, 2020 at 9:44 PM
Updated November 3, 2020 at 10:19 AM
Resolved October 30, 2020 at 6:37 PM