Details
-
Test
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
-
None
-
New
Description
I think MockRandomMergePolicy should just wrap the reader in a no-op filter reader? This better simulates the case of e.g. users upgrading lucene over an old index, some segments bulk-merge eligible, others not, etc.