You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Adrien Grand (JIRA)" <ji...@apache.org> on 2014/02/28 13:51:20 UTC

[jira] [Updated] (LUCENE-5481) IndexWriter.forceMerge may run unneeded merges

     [ https://issues.apache.org/jira/browse/LUCENE-5481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Adrien Grand updated LUCENE-5481:
---------------------------------

    Attachment: LUCENE-5481.patch

Here is an attempt to fit it. The interesting change is in {{MergePolicy.isMerged}}.

> IndexWriter.forceMerge may run unneeded merges
> ----------------------------------------------
>
>                 Key: LUCENE-5481
>                 URL: https://issues.apache.org/jira/browse/LUCENE-5481
>             Project: Lucene - Core
>          Issue Type: Bug
>            Reporter: Adrien Grand
>            Assignee: Adrien Grand
>            Priority: Minor
>             Fix For: 4.8
>
>         Attachments: LUCENE-5481.patch
>
>
> I was running some tests and was surprised that {{IndexWriter.forceMerge}} caused the index to be merged even when the index contains a single segment with no deletions.
> This is due to {{MergePolicy.isMerged}} which always returns false with the default configuration although merge policies rely on it to know whether a single-segment index should be merged.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org