Mailing-List: contact java-user-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: java-user@lucene.apache.org
Received-SPF: pass (athena.apache.org: domain of varunthacker1989@gmail.com
 designates 209.85.215.44 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CALfq-2RkKWPpyeNQoJ5uRSGKgeTTJsF=Ur3ajbsNWT=yNund8w@mail.gmail.com>
References: 
 <CAEH2wZDEfUQjVYno4dPVBvZkoGYF-RcEp3+Y9cjdrzwqSgVYfg@mail.gmail.com>
 <CAOdYfZXXyVSf9+xYaRhr5v2O4Mc6S2v-qWuT112_CJFYhWTPqw@mail.gmail.com>
 <CALfq-2RkKWPpyeNQoJ5uRSGKgeTTJsF=Ur3ajbsNWT=yNund8w@mail.gmail.com>
From: Varun Thacker <varunthacker1989@gmail.com>
Date: Tue, 29 Apr 2014 17:52:00 +0530
Message-ID: 
 <CAEH2wZCWynEUKOzgidMWtEzX86Dh7GTxdxKdXHY2Ja+BPnbyrQ@mail.gmail.com>
Subject: Re: No Compound Files
To: java-user <java-user@lucene.apache.org>
Content-Type: multipart/alternative; boundary=001a11c24184c57c9d04f82d7bd7

--001a11c24184c57c9d04f82d7bd7
Content-Type: text/plain; charset=UTF-8

Thanks for the response. I was not aware of  IWC.setUseCompoundFile .

@Shai this is what I feel is confusing - From what I understand
NoMergePolicy means no merges. Hence why have two separate options?


On Tue, Apr 29, 2014 at 5:44 PM, Shai Erera <serera@gmail.com> wrote:

> 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 <rcmuir@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
> > <varunthacker1989@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-unsubscribe@lucene.apache.org
> > For additional commands, e-mail: java-user-help@lucene.apache.org
> >
> >
>


-- 


Regards,
Varun Thacker
http://www.vthacker.in/

--001a11c24184c57c9d04f82d7bd7--