lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Earwin Burrfoot (JIRA)" <j...@apache.org>
Subject [jira] Commented: (LUCENE-1648) when you clone or reopen an IndexReader with pending changes, the new reader doesn't commit the changes
Date Sun, 07 Jun 2009 20:01:07 GMT

    [ https://issues.apache.org/jira/browse/LUCENE-1648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12717089#action_12717089
] 

Earwin Burrfoot commented on LUCENE-1648:
-----------------------------------------

As LUCENE-1651 is now committed, this issue can be resolved.

> 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


Mime
View raw message