lucene-solr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ryan McKinley (JIRA)" <>
Subject [jira] Updated: (SOLR-182) register SolrRequestHandlers at runtime / lazy loading
Date Wed, 07 Mar 2007 02:31:24 GMT


Ryan McKinley updated SOLR-182:

    Attachment: SOLR-182-RuntimeRequestHandlers.patch

This update loads handlers in the style suggested by Hoss.

It makes sure everything is instanciated and registered before calling init() on any handlres
registered in solrconfig.xml

It calls init() on handlers in the order they were defined.

The only open issue is if SolrCore.getRequestHandler() should be synchronized.  I can't think
of any potential problems if it isn't but i could be missing something.

I'll let whoever commits this decide if it should be synchronized or not.

> register SolrRequestHandlers at runtime / lazy loading
> ------------------------------------------------------
>                 Key: SOLR-182
>                 URL:
>             Project: Solr
>          Issue Type: Improvement
>            Reporter: Ryan McKinley
>             Fix For: 1.2
>         Attachments: SOLR-182-RuntimeRequestHandlers.patch, SOLR-182-RuntimeRequestHandlers.patch,
SOLR-182-RuntimeRequestHandlers.patch, SOLR-182-RuntimeRequestHandlers.patch
> It would be useful to be able to register handlers after SolrCore has been initialized
initialized.  It is also useful to be able to ask what handlers are registered and to where.
 This patch adds the following functions to SolrCore:
> SolrRequestHandler registerRequestHandler(String handlerName, SolrRequestHandler handler);
> Collection<SolrRequestHandler> getRequestHandlers(Class<? extends SolrRequestHandler>
> It also guarantees that request handlers will be initialized with an argument saying
what path it is registered to.  RequestHandlerBase gets a bean for the registered path.
> While discussing this, Yonik suggested making it possible to defer initialization of
some handlers that will be infrequently used.  I added the 'LazyRequestHandlerWrapper'  (if
taking this out makes the patch any easier to commit - it can get its own issue)
> check:

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message