[
https://issues.apache.org/jira/browse/LUCENE-5481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13915740#comment-13915740
]
Michael McCandless commented on LUCENE-5481:
--------------------------------------------
That's just awful.
So if you .forceMerge(1) an existing index, and then turn around call call that
again, the 2nd time still does the merge?
> 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-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
