Resetting a database index with IndexedRelations.reset does not properly clear the IndexedRelationsSearcher caches
Kind of similar to #725 (closed), IndexedRelationsImpl.reset
does not call searcher.bestEffortClear(monitor, processor.getSession())
which it should call to ensure all caches are properly reset. Currently it just deletes the files on disk.
When index resetting facilities are (usually manually) used, this can cause unexpected behaviour by returning old cached results instead of returning re-indexed results from the actual database.