[
https://issues.apache.org/jira/browse/LUCENE-5672?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14059449#comment-14059449
]
Mark Miller commented on LUCENE-5672:
-------------------------------------
bq. The user can freely configure this with MergePolicy. Its no different from
any other index operation. This is a bug.
I was leaning towards Shai's argument at first, but after a bit of deeper
thought, I agree with Robert.
I don't know that having an option to not use the merge policy will add any
confusion if the default is right, but it does seem the merge policy itself is
sufficient for cases I can think of. I don't know that you need this extra way
to control merges.
> 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]
