[LUCENE-2600] don't try to cache a composite reader's MultiBits deletedDocs - ASF JIRA

XML

Word

Printable

JSON

Details

Type: Bug
Status: Resolved
Priority: Major
Resolution: Fixed
Affects Version/s: None
Fix Version/s: 4.0-ALPHA
Component/s: None
Labels:
None

Lucene Fields:

New

Description

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.

Attachments

- Sort By Name
- Sort By Date
- Ascending
- Descending

LUCENE-2600.patch
14/Aug/10 13:33
50 kB
Michael McCandless
LUCENE-2600.patch
12/Aug/10 10:55
9 kB
Michael McCandless

Activity

People

Assignee:: Michael McCandless

Reporter:: Michael McCandless

Votes:: 0 Vote for this issue

Watchers:: 0 Start watching this issue

Dates

Created:: 12/Aug/10 10:54

Updated:: 26/Oct/22 16:34

Resolved:: 30/Aug/10 16:56