lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason Rutherglen (JIRA)" <>
Subject [jira] Updated: (LUCENE-1314) IndexReader.reopen(boolean force)
Date Sun, 29 Jun 2008 15:17:45 GMT


Jason Rutherglen updated LUCENE-1314:

    Attachment: lucene-1314.patch


Added fieldsReaderLocal to SegmentReader.  reopenSegment passed the fieldsReaderLocal and
termVectorsLocal to the new SegmentReader.  In the current version, a new termVectorsLocal
is created for each SegmentReader which made reuse of the previously created TermVectorsReaders
for a thread unavailable.  The same is implemented for fieldsReaderLocal.  

The locking needs a default mechanism.  For my own purposes I will likely turn it off, the
bug I posted was really the fault of the Ocean code since fixed.  

Would like to be able to optionally have this line run in DirectoryIndexReader in reopen.
 Does it need to be run on a clone?

SegmentInfos infos = new SegmentInfos();, segmentFileName);

> IndexReader.reopen(boolean force)
> ---------------------------------
>                 Key: LUCENE-1314
>                 URL:
>             Project: Lucene - Java
>          Issue Type: New Feature
>          Components: Index
>    Affects Versions: 2.3.1
>            Reporter: Jason Rutherglen
>            Assignee: Michael McCandless
>            Priority: Minor
>         Attachments: lucene-1314.patch, lucene-1314.patch, lucene-1314.patch, lucene-1314.patch
> Based on discussion 
The problem is reopen returns the same reader if there are no changes, so if docs are deleted
from the new reader, they are also reflected in the previous reader which is not always desired

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:
For additional commands, e-mail:

View raw message