[
https://issues.apache.org/jira/browse/LUCENE-847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12518520
]
Ning Li commented on LUCENE-847:
--------------------------------
> Furthermore, I think this is all contained within IndexWriter, right?
> Ie when we go to "replace/checkin" the newly merged segment, this
> "merge newly flushed deletes" would execute at that time. And, I
> think, we would block flushes while this is happening, but
> addDocument/deleteDocument/updateDocument would still be allowed?
Yes and yes. :-)
> Couldn't we also just update the docIDs of pending deletes, and not
> flush? Ie we know the mapping of old -> new docID caused by the
> merge, so we can run through all deleted docIDs and remap?
Hmm, I was worried quite a number of delete docIDs could be buffered,
but I guess it's still better than having to do a flush. So yes, this is better!
> 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
> Attachments: concurrentMerge.patch, LUCENE-847.patch.txt,
> 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]
