lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael McCandless (JIRA)" <j...@apache.org>
Subject [jira] Updated: (LUCENE-2600) don't try to cache a composite reader's MultiBits deletedDocs
Date Thu, 12 Aug 2010 10:57:15 GMT

     [ https://issues.apache.org/jira/browse/LUCENE-2600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Michael McCandless updated LUCENE-2600:
---------------------------------------

    Attachment: LUCENE-2600.patch

Attached patch, removing the caching altogether.

> don't try to cache a composite reader's MultiBits deletedDocs
> -------------------------------------------------------------
>
>                 Key: LUCENE-2600
>                 URL: https://issues.apache.org/jira/browse/LUCENE-2600
>             Project: Lucene - Java
>          Issue Type: Bug
>            Reporter: Michael McCandless
>            Assignee: Michael McCandless
>             Fix For: 4.0
>
>         Attachments: LUCENE-2600.patch
>
>
> MultiFields.getDeletedDocs now builds up a MultiBits instance (so that one can check
if a top-level docID is deleted), but it now stuffs it into a private cache on IndexReader.
> This is invalid when the composite reader is read/write, and can result in a MultiReader
falsely claiming a doc was not deleted.

-- 
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: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message