The problem is that compound files settings are split between MergePolicy and IndexWriterConfig. As documented on IWC.setUseCompoundFile, this setting controls how new segments are flushed, while the MP setting controls how merged segments are written.
If we only offer NoMP.INSTANCE, what would it do w/ merged segments? always compound? always not-compound? But that won't solve the problem of new flushed segments, since that's controlled by IWC. If we can move all of that to IWC, I think it will remove the confusion.. it always confuses me that I use NoMP.COMPUND, yet I see non-compound segments, until I remember to change the IWC setting. Shai On Tue, Apr 29, 2014 at 3:07 PM, Robert Muir <rcm...@gmail.com> 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 > <varunthacker1...@gmail.com> 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: java-user-unsubscr...@lucene.apache.org > For additional commands, e-mail: java-user-h...@lucene.apache.org > >
