[
https://issues.apache.org/jira/browse/LUCENE-5672?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14059455#comment-14059455
]
Robert Muir commented on LUCENE-5672:
-------------------------------------
FYI: this is the third time i've heard of this trap hitting people and creating
hundreds or thousands of index segments: once was from coworkers at a past job,
twice was lucene user list discussion "Merger performance degradation on
3.6.1", thrice was Erick's recent ML post.
For people that don't want merging they have NoMergePolicy, maybeMerge() is
even documented as "expert" and "Explicit calls to maybeMerge() are usually not
necessary. The most common case is when merge policy parameters have changed".
So requiring the user to manually invoke this after index operations to prevent
segment explosion is wrong IMO.
> Addindexes does not call maybeMerge
> -----------------------------------
>
> Key: LUCENE-5672
> URL: https://issues.apache.org/jira/browse/LUCENE-5672
> Project: Lucene - Core
> Issue Type: Bug
> Reporter: Robert Muir
> Assignee: Robert Muir
> Attachments: LUCENE-5672.patch
>
>
> I don't know why this was removed, but this is buggy and just asking for
> trouble.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
