x27;ve been experimenting with factoring the merge policy out of
IndexWriter and making it pluggable. In such a world, IndexWriter would
still do all the merges, but it would delegate the decision on what
segments to merge to a merge policy:
interface MergePolicy {
static class MergeSpecifi
There is very little about IndexWriter that I understand, but i am very
much in favor of the spirit of your idea (your message is one of the
things that prompted me to polish/open LUCENE-831 for a correlary issue
about IndexReader caching)
: void merge( SegmentInfos segmentInfos )
: