Details
-
Bug
-
Status: Resolved
-
Normal
-
Resolution: Fixed
-
None
-
None
-
Normal
Description
In AbstractThreadUnsafePartition, repeated slice() calls on a RowSearcher can produce incorrect results. This is caused by only performing a binary search over a sublist (based on nextIdx), but not taking nextIdx into account when using the search result index.
I made a quick fix in this commit on one of my branches, but the full fix also needs to cover ReverseRowSearcher and include a test to reproduce the issue.