You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Commit Tag Bot (JIRA)" <ji...@apache.org> on 2013/05/02 18:46:17 UTC
[jira] [Commented] (LUCENE-4967) Absorb NRTManager entirely into a
separate reopen thread class
[ https://issues.apache.org/jira/browse/LUCENE-4967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13647685#comment-13647685 ]
Commit Tag Bot commented on LUCENE-4967:
----------------------------------------
[trunk commit] mikemccand
http://svn.apache.org/viewvc?view=revision&revision=1478438
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: 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