[
https://issues.apache.org/jira/browse/LUCENE-4472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13476920#comment-13476920
]
Michael McCandless commented on LUCENE-4472:
--------------------------------------------
Actually I think we only need to add the MergeCause (maybe rename this to
MergeTrigger?) param to findMerges? That method is invoked for natural merges,
and knowing the trigger for the natural merge is useful...
The other two methods (findForceMerges, findForcedDeletesMerges) are only
triggered when the app explicitly asked IndexWriter to do so.
> Add setting that prevents merging on updateDocument
> ---------------------------------------------------
>
> Key: LUCENE-4472
> URL: https://issues.apache.org/jira/browse/LUCENE-4472
> Project: Lucene - Core
> Issue Type: Improvement
> Components: core/index
> Affects Versions: 4.0
> Reporter: Simon Willnauer
> Fix For: 4.1, 5.0
>
> Attachments: LUCENE-4472.patch, LUCENE-4472.patch
>
>
> Currently we always call maybeMerge if a segment was flushed after
> updateDocument. Some apps and in particular ElasticSearch uses some hacky
> workarounds to disable that ie for merge throttling. It should be easier to
> enable this kind of behavior.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
