[
https://issues.apache.org/jira/browse/LUCENE-1648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12711378#action_12711378
]
Earwin Burrfoot commented on LUCENE-1648:
-----------------------------------------
I wonder if the only two tests I still have failing for always-use-MSR patch
are somehow related to this. They are:
testSegmentReaderDelDocsReferenceCounting(org.apache.lucene.index.TestIndexReaderClone)
testNormsRefCounting(org.apache.lucene.index.TestIndexReaderCloneNorms)
Both die with an exception similar to
java.io.IOException: file "_0_1.del" was already written to
And I didn't yet have time to fully grok what's happening there. :/
I do modifications through toplevel readers, assert state of their only segment
reader and everything goes well until .flush() or .close() on toplevel reader.
> when you clone or reopen an IndexReader with pending changes, the new reader
> doesn't commit the changes
> -------------------------------------------------------------------------------------------------------
>
> Key: LUCENE-1648
> URL: https://issues.apache.org/jira/browse/LUCENE-1648
> Project: Lucene - Java
> Issue Type: Bug
> Components: Index
> Reporter: Michael McCandless
> Assignee: Michael McCandless
> Priority: Minor
> Fix For: 2.9
>
>
> While working on LUCENE-1647, I came across this issue... we are failing to
> carry over hasChanges, norms/deletionsDirty, etc, when cloning the new reader.
--
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
