[
https://issues.apache.org/jira/browse/LUCENE-847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12527304
]
Michael McCandless commented on LUCENE-847:
-------------------------------------------
> Looks like some anomalous tests. Last night I checked twice, but
> today results are: 58 to 48 in favor of Concurrent. I am going to
> assume my first results where invalid. Sorry for the noise and
> thanks for the great patch.
OK, phew!
> Has passed quite a few stress tests I run on my app without any
> problems so far.
I'm glad to hear that :) Thanks for being such an early adopter!
> Do both merge policies allow for a closer to constant add time or is
> it just the Concurrent policy?
Not sure I understand the question -- you mean addDocument? Yes it's
only ConcurrentMergeScheduler that should keep addDocument calls
constant time, because SerialMergeScheduler will hijack the addDocument
thread to do its merges.
> Factor merge policy out of IndexWriter
> --------------------------------------
>
> Key: LUCENE-847
> URL: https://issues.apache.org/jira/browse/LUCENE-847
> Project: Lucene - Java
> Issue Type: Improvement
> Components: Index
> Reporter: Steven Parkes
> Assignee: Steven Parkes
> Fix For: 2.3
>
> Attachments: concurrentMerge.patch, LUCENE-847.patch.txt,
> LUCENE-847.patch.txt, LUCENE-847.take3.patch, LUCENE-847.take4.patch,
> LUCENE-847.take5.patch, LUCENE-847.take6.patch, LUCENE-847.take7.patch,
> LUCENE-847.txt
>
>
> If we factor the merge policy out of IndexWriter, we can make it pluggable,
> making it possible for apps to choose a custom merge policy and for easier
> experimenting with merge policy variants.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
