[
https://issues.apache.org/jira/browse/LUCENE-743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12535362
]
Michael Busch commented on LUCENE-743:
--------------------------------------
{quote}
So I think deleteDocument(int id) should either be moved to a subclass. same
with setNorms?
{quote}
Or we could take the approach you suggested in
http://www.gossamer-threads.com/lists/lucene/java-dev/52017.
That would mean to add a callback after flush to get a current IndexReader to
get the docids and to use the IndexWriter then to perform deleteDocument(docId)
or setNorm(). These methods could also take an IndexReader as argument, e. g.
deleteDocument(IndexReader reader, int docId), which would throw an IOException
if the passed in reader is stale (i. e. docids have changed since the reader
was opened). Just as IndexReader does it today. Does this make sense or am I
missing something?
> 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]
