lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yonik Seeley (JIRA)" <>
Subject [jira] Commented: (LUCENE-743) IndexReader.reopen()
Date Wed, 17 Oct 2007 21:02:51 GMT


Yonik Seeley commented on LUCENE-743:

As for reopen() I'd like to go with Hoss' suggestion for now and add warning comments to reopen()
saying that using an re-opened IndexReader with closeOldReader==false for write operations
will result in an undefined behavior.

How about just defining the behavior such that any pending changes are flushed.  That would
make it more useful because you could then reopen readers you used for deletes.  An alternative
would be a method to explicitly flush changes on a reader, giving one the ability to then
reopen it, but  I like the former better since it avoids adding another API call.

> 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