lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Commit Tag Bot (JIRA)" <>
Subject [jira] [Commented] (LUCENE-4967) Absorb NRTManager entirely into a separate reopen thread class
Date Thu, 02 May 2013 17:06:15 GMT


Commit Tag Bot commented on LUCENE-4967:

[branch_4x commit] mikemccand

LUCENE-4967: move NRTManager entirely into a reopen thread so it can interact with any ReferenceManager
> Absorb NRTManager entirely into a separate reopen thread class
> --------------------------------------------------------------
>                 Key: LUCENE-4967
>                 URL:
>             Project: Lucene - Core
>          Issue Type: Improvement
>            Reporter: Michael McCandless
>            Assignee: Michael McCandless
>             Fix For: 5.0, 4.4
>         Attachments: LUCENE-4967.patch
> I think NRTManager can be drastically simplified by moving all of its
> logic into a new reopen thread class.  All logic for waiting for a
> specific generation and reopening at different rates would live in
> this class.
> This would fully decouple the "wait for generation X to be visible"
> from which particular ReferenceManager impl you're using, which would
> make it possible to use the controlled consistency approach of
> NRTManager with any managers (e.g. SearcherTaxonomyManager).

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message