NoMP means no merges, and indeed it seems silly that NoMP distinguishes between compound/non-compound settings. Perhaps it's rooted somewhere in the past, I don't remember.
I checked and IndexWriter.addIndexes consults MP.useCompoundFile(segmentInfo) when it adds the segments. But maybe NoMP.useCompoundFile can be changed to return newSegment.info.isCompoundFile? I.e. it doesn't change the type of the new segment? Shai On Tue, Apr 29, 2014 at 3:50 PM, Michael McCandless < [email protected]> wrote: > +1 to just have NoMergePolicy.INSTANCE > > Mike McCandless > > http://blog.mikemccandless.com > > > On Tue, Apr 29, 2014 at 8:07 AM, Robert Muir <[email protected]> wrote: > > I think NoMergePolicy.NO_COMPOUND_FILES and > > NoMergePolicy.COMPOUND_FILES should be removed, and replaced with > > NoMergePolicy.INSTANCE > > > > If you want to change whether CFS is used by indexwriter flush, you > > need to set that in IndexWriterConfig. > > > > On Tue, Apr 29, 2014 at 8:03 AM, Varun Thacker > > <[email protected]> wrote: > >> I wanted to use the NoMergePolicy.NO_COMPOUND_FILES to ensure that no > >> merges take place on the index. However I was unsuccessful at it. What > I am > >> doing wrong here. > >> > >> Attaching a gist with - > >> 1. Output when using NoMergePolicy.NO_COMPOUND_FILES > >> 2. Output when using TieredMergePolicy with policy.setNoCFSRatio(0.0) > >> 3. The code snippet I used. > >> > >> https://gist.github.com/vthacker/11398124 > >> > >> I tried it using Lucene 4.7 > >> > >> > >> > >> > >> > >> -- > >> > >> > >> Regards, > >> Varun Thacker > >> http://www.vthacker.in/ > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
