lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Busch (JIRA)" <>
Subject [jira] Commented: (LUCENE-743) IndexReader.reopen()
Date Thu, 18 Oct 2007 20:45:51 GMT


Michael Busch commented on LUCENE-743:

The implementation seems simple. When a reader is opened, it starts with RC 1. When it is
closed, it decrefs the RC and marks itself closed (to make sure double-close does not re-decref
the RC). When a MultiReader needs to use the reader, it calls incref. And when that MultiReader
is done with it, it calls decref. Whenever the RC hits 0 it's safe to free all resources.

Wouldn't that work?

You're right, for a MultiReader and ParallelReader this would work and wouldn't be hard to

It is quite different when it comes to SegmentReaders. SegmentReader.reopen() checks SegmentInfos
if there is a segment with the same name but newer normGen or delGen. If there is one then
a new SegmentReader instance is created that reuses resources like e. g. TermInfosReader and
loads the new generation of the del or norm file.

Now you can end up having a bunch of SegmentReaders that share the same resources but don't
know about each other. The reference counting would have to happen somewhere else, e. g. in
the TermInfosReader. Of course this is doable, but it's a special case and more complicated
compared to the "restrict reopen() to only be called once"-approach.

> IndexReader.reopen()
> --------------------
>                 Key: LUCENE-743
>                 URL:
>             Project: Lucene - Java
>          Issue Type: Improvement
>          Components: Index
>            Reporter: Otis Gospodnetic
>            Assignee: Michael Busch
>            Priority: Minor
>             Fix For: 2.3
>         Attachments:, lucene-743-take2.patch, lucene-743.patch,
lucene-743.patch, lucene-743.patch,,, varient-no-isCloneSupported.BROKEN.patch
> This is Robert Engels' implementation of IndexReader.reopen() functionality, as a set
of 3 new classes (this was easier for him to implement, but should probably be folded into
the core, if this looks good).

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