[
https://issues.apache.org/jira/browse/LUCENE-1589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12696837#action_12696837
]
Jason Rutherglen commented on LUCENE-1589:
------------------------------------------
I took a walk and thought about this, it seems that we do not
need to write any new code, we can simply ref and clone
addIndexesNoOptimize(IndexReader[] readers) to
MergePolicy.OneMerge.readers/readersClone. Meaning the problem
of new deletes while merging is solved? Of course this would
imply we synchronize on the source reader in commitMergedDeletes
(because deleteDocument is synced?)
> IndexWriter.addIndexesNoOptimize(IndexReader[] readers)
> -------------------------------------------------------
>
> Key: LUCENE-1589
> URL: https://issues.apache.org/jira/browse/LUCENE-1589
> Project: Lucene - Java
> Issue Type: Improvement
> Components: Index
> Affects Versions: 2.4.1
> Reporter: Jason Rutherglen
> Priority: Minor
> Fix For: 2.9
>
> Original Estimate: 168h
> Remaining Estimate: 168h
>
> Similar to IndexWriter.addIndexesNoOptimize(Directory[] dirs)
> but for IndexReaders. This will be used to flush cloned ram
> indexes to disk for near realtime indexing.
--
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: java-dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: java-dev-h...@lucene.apache.org
