lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Commit Tag Bot (JIRA)" <>
Subject [jira] [Commented] (LUCENE-4986) NRT reader doesn't see changes after successful IW.tryDeleteDocument
Date Thu, 09 May 2013 14:14:43 GMT


Commit Tag Bot commented on LUCENE-4986:

[trunk commit] mikemccand

LUCENE-4986: NRT reopen after tryDeleteDocument was failing to reflect the deletion
> NRT reader doesn't see changes after successful IW.tryDeleteDocument
> --------------------------------------------------------------------
>                 Key: LUCENE-4986
>                 URL:
>             Project: Lucene - Core
>          Issue Type: Bug
>          Components: core/index
>            Reporter: Michael McCandless
>            Assignee: Michael McCandless
>             Fix For: 5.0, 4.4
>         Attachments: LUCENE-4986.patch, LUCENE-4986.patch
> Reported by Reg on the java-user list, subject "TrackingIndexWriter.tryDeleteDocument(IndexReader,
int) vs deleteDocuments(Query)":
> When IW.tryDeleteDocument succeeds, it marks the document as deleted in the pending BitVector
in ReadersAndLiveDocs, but then when the NRT reader checks if it's still current by calling
IW.nrtIsCurrent, we fail to catch changes to the BitVector, resulting in the NRT reader thinking
it's current and not reopening.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message