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] Updated: (LUCENE-1648) when you clone or reopen an IndexReader with pending changes, the new reader doesn't commit the changes
Date Thu, 21 May 2009 12:05:45 GMT

     [ 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

bq. Bad news is something is wrong w/ your patch, because MSR needs to carry over hasChanges/deletions/norms
on clone().
Something is wrong with trunk.
Try the test in the patch. It is absolutely identical to yours, except it adds another doc
to index to have two segments and consequently MSR.

> 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.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