You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Michael McCandless (JIRA)" <ji...@apache.org> on 2009/06/07 22:12:07 UTC
[jira] Resolved: (LUCENE-1648) when you clone or reopen an
IndexReader with pending changes, the new reader doesn't commit the changes
[ https://issues.apache.org/jira/browse/LUCENE-1648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael McCandless resolved LUCENE-1648.
----------------------------------------
Resolution: Fixed
> 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-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-dev-help@lucene.apache.org