You are viewing a plain text version of this content. The canonical link for it is here.
Posted to solr-dev@lucene.apache.org by Noble Paul നോബിള് नोब्ळ् <no...@gmail.com> on 2009/04/25 07:17:56 UTC
Re: [jira] Commented: (SOLR-1106) Pluggable CoreAdminHandler (Action
) architecture that allows for custom handler access to CoreContainer /
request-response
documentation looks good. But, it should add a note that it is a 1.4 feature.
see example http://wiki.apache.org/solr/Solrj#head-2046bbaba3759b6efd0e33e93f5502038c01ac65
On Wed, Apr 22, 2009 at 7:56 PM, Kay Kay (JIRA) <ji...@apache.org> wrote:
>
> [ https://issues.apache.org/jira/browse/SOLR-1106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12701546#action_12701546 ]
>
> Kay Kay commented on SOLR-1106:
> -------------------------------
>
> I have submitted changes to the wiki at - http://wiki.apache.org/solr/CoreAdmin with additional info about adminHandler introduced in this jira. Let me know how it looks and approve the same once this fix is in.
>
>> Pluggable CoreAdminHandler (Action ) architecture that allows for custom handler access to CoreContainer / request-response
>> -----------------------------------------------------------------------------------------------------------------------------
>>
>> Key: SOLR-1106
>> URL: https://issues.apache.org/jira/browse/SOLR-1106
>> Project: Solr
>> Issue Type: New Feature
>> Components: search
>> Environment: Java 5, Tomcat 6
>> Reporter: Kay Kay
>> Assignee: Shalin Shekhar Mangar
>> Fix For: 1.4
>>
>> Attachments: SOLR-1106.patch, SOLR-1106.patch, SOLR-1106.patch, SOLR-1106.patch, SOLR-1106.patch
>>
>> Original Estimate: 3h
>> Remaining Estimate: 3h
>>
>> Currently there are certain default actions implemented in CoreAdminHandler ( CREATE , SWAP, RELOAD , ALIAS etc.) .
>> For the purpose of in-house monitoring tools that needs to interact with multiple cores at a given solr instance - we need custom handlers that has access to CoreContainer and the req, resp of the same.
>> So - the proposed way of injecting handlers is as follows.
>> In solr.xml - we add a new schema -
>> <solr >
>> <cores adminPath="/cores/admin">
>>
>> <adminActionHandler action="newaction" handlerType="com.mydomain.myclass" />
>> </cores>
>> </solr>
>> New abstract class - CoreAdminActionRequestHandler added - that com.mydomain.myclass would need to inherit from.
>> Following action handlers registered by default -
>> registerCustomAdminHandler("create", new AdminCreateActionRequestHandler());
>> registerCustomAdminHandler("rename", new AdminRenameActionRequestHandler());
>> registerCustomAdminHandler("alias", new AdminAliasActionRequestHandler());
>> registerCustomAdminHandler("unload", new AdminUnloadActionRequestHandler());
>> registerCustomAdminHandler("status", new AdminStatusActionRequestHandler());
>> registerCustomAdminHandler("persist", new AdminPersistActionRequestHandler());
>> registerCustomAdminHandler("reload", new AdminReloadActionRequestHandler());
>> registerCustomAdminHandler("swap", new AdminSwapActionRequestHandler());
>> Trying to register a handler with one that already exists would result in an error ( Hence - the above mentioned defaults would not be overridden).
>
> --
> This message is automatically generated by JIRA.
> -
> You can reply to this email to add a comment to the issue online.
>
>
--
--Noble Paul