lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Earwin Burrfoot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (LUCENE-2904) non-contiguous LogMergePolicy should be careful to not select merges already running
Date Thu, 05 May 2011 16:15:03 GMT

    [ https://issues.apache.org/jira/browse/LUCENE-2904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13029408#comment-13029408
] 

Earwin Burrfoot commented on LUCENE-2904:
-----------------------------------------

Ok, I'm wrong. We need both a list of all SIs and eligible SIs for calculations. But that
should be handled through API change, not a new public method on IW.

> non-contiguous LogMergePolicy should be careful to not select merges already running
> ------------------------------------------------------------------------------------
>
>                 Key: LUCENE-2904
>                 URL: https://issues.apache.org/jira/browse/LUCENE-2904
>             Project: Lucene - Java
>          Issue Type: Bug
>            Reporter: Michael McCandless
>            Assignee: Michael McCandless
>            Priority: Minor
>             Fix For: 3.2, 4.0
>
>         Attachments: LUCENE-2904.patch
>
>
> Now that LogMP can do non-contiguous merges, the fact that it disregards which segments
are already being merged is more problematic since it could result in it returning conflicting
merges and thus failing to run multiple merges concurrently.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

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


Mime
View raw message