[
https://issues.apache.org/jira/browse/LUCENE-743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12535970
]
Yonik Seeley commented on LUCENE-743:
-------------------------------------
{quote}
A reader which is being used for deletes or setting norms is always current (it
owns the write lock), so there should never be the need to re-open such a
reader.
{quote}
I was thinking about the "add some docs" then "delete some docs" scenario:
One currently needs to close() the deleting reader to open an IndexWriter. If
IndexReader.commit() was public, then one could simply flush changes, and then
call reopen() after the IndexWriter was done adding new documents. But perhaps
longer term, all deletions should be done via the IndexWriter anyway.
{quote}
if you re-open an existing reader which was not used for deletes before and use
the new instance (b) to perform deletes
{quote}
Ah, thanks for that clarification. I guess that should remain undefined.
> IndexReader.reopen()
> --------------------
>
> Key: LUCENE-743
> URL: https://issues.apache.org/jira/browse/LUCENE-743
> Project: Lucene - Java
> Issue Type: Improvement
> Components: Index
> Reporter: Otis Gospodnetic
> Assignee: Michael Busch
> Priority: Minor
> Fix For: 2.3
>
> Attachments: IndexReaderUtils.java, lucene-743-take2.patch,
> lucene-743.patch, lucene-743.patch, lucene-743.patch, MyMultiReader.java,
> MySegmentReader.java, varient-no-isCloneSupported.BROKEN.patch
>
>
> This is Robert Engels' implementation of IndexReader.reopen() functionality,
> as a set of 3 new classes (this was easier for him to implement, but should
> probably be folded into the core, if this looks good).
--
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]
