[
https://issues.apache.org/jira/browse/LUCENE-1314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12609071#action_12609071
]
Michael McCandless commented on LUCENE-1314:
--------------------------------------------
bq. Using the patch and the above subclass of SegmentReader received the
following bug. I am assuming it has something to do with SegmentInfos
committing. Ideally the new clone method of IndexReader will avoid things like
reloading SegmentInfos from disk each time. That will probably slow down the
rapid updates too much.
Right, that exception happens because you are carrying your own deletedDocs in
memory to the new SegmentReader without first saving them to the _X_N.del file
for that segment. The new clone() approach definitely should not reload the
segments_N file, and thus not call SegmentReader.initialize.
> IndexReader.reopen(boolean force)
> ---------------------------------
>
> Key: LUCENE-1314
> URL: https://issues.apache.org/jira/browse/LUCENE-1314
> Project: Lucene - Java
> Issue Type: New Feature
> Components: Index
> Affects Versions: 2.3.1
> Reporter: Jason Rutherglen
> Assignee: Michael McCandless
> Priority: Minor
> Attachments: lucene-1314.patch, lucene-1314.patch, lucene-1314.patch
>
>
> Based on discussion
> http://www.nabble.com/IndexReader.reopen-issue-td18070256.html. The problem
> is reopen returns the same reader if there are no changes, so if docs are
> deleted from the new reader, they are also reflected in the previous reader
> which is not always desired behavior.
--
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]
