[
https://issues.apache.org/jira/browse/LUCENE-1648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Earwin Burrfoot updated LUCENE-1648:
------------------------------------
Attachment: LUCENE-1648-followup.patch
And here's the fix.
The problem - it's not elegant at all. We can scrap it and I can do the fix
within "always use MSR" patch, it looks way cleaner there.
> 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
>
> Attachments: LUCENE-1648-followup.patch, LUCENE-1648-followup.patch,
> LUCENE-1648.patch
>
>
> 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
