lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael McCandless (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (LUCENE-4967) Absorb NRTManager entirely into a separate reopen thread class
Date Thu, 02 May 2013 17:08:15 GMT

     [ https://issues.apache.org/jira/browse/LUCENE-4967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Michael McCandless resolved LUCENE-4967.
----------------------------------------

    Resolution: Fixed
    
> Absorb NRTManager entirely into a separate reopen thread class
> --------------------------------------------------------------
>
>                 Key: LUCENE-4967
>                 URL: https://issues.apache.org/jira/browse/LUCENE-4967
>             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: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message