Created LUCENE-5633 for it.
On Tue, Apr 29, 2014 at 6:28 PM, Shai Erera wrote:
> 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.addInde
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.useCo
+1 to just have NoMergePolicy.INSTANCE
Mike McCandless
http://blog.mikemccandless.com
On Tue, Apr 29, 2014 at 8:07 AM, Robert Muir wrote:
> I think NoMergePolicy.NO_COMPOUND_FILES and
> NoMergePolicy.COMPOUND_FILES should be removed, and replaced with
> NoMergePolicy.INSTANCE
>
> If you want t
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 wrote:
> The problem is that compound files se
On Tue, Apr 29, 2014 at 8:14 AM, Shai Erera wrote:
>
> If we only offer NoMP.INSTANCE, what would it do w/ merged segments? always
> compound? always not-compound?
it doesnt merge though.
-
To unsubscribe, e-mail: java-user-unsu
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
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
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.setNoC
