You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Noble Paul (JIRA)" <ji...@apache.org> on 2014/11/27 14:16:12 UTC
[jira] [Updated] (SOLR-6607) Managing requesthandlers through API
[ https://issues.apache.org/jira/browse/SOLR-6607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Noble Paul updated SOLR-6607:
-----------------------------
Summary: Managing requesthandlers through API (was: Registering requesthandlers through API)
> Managing requesthandlers through API
> ------------------------------------
>
> Key: SOLR-6607
> URL: https://issues.apache.org/jira/browse/SOLR-6607
> Project: Solr
> Issue Type: Sub-task
> Reporter: Noble Paul
> Assignee: Noble Paul
> Attachments: SOLR-6607.patch
>
>
> The concept of solrconfig editing is split into multiple pieces . This issue is about registering components and uploading binaries through an API.
> This supports multiple operations
> * commands 'create-requesthandler', "update-requesthandler","delete-requesthandler" which can set the configuration of a component . This configuration will be saved inside the configoverlay.json
> The components has to be available in the classpath of all nodes.
> example for registering a component
> {code}
> curl http://localhost:8983/solr/collection1/config -H -d '{
> "create-requesthandler" : {"name": "/mypath" ,
> "class":"com.mycomponent.ClassName" ,
> "defaults":{"x":"y" ," a":"b"}
> },
> "update-requesthandler" :{"name": "/mypath" ,
> "class":"com.mycomponent.ClassName" ,
> "startup":"lazy" ,
> "defaults":{"x":"y" ," a":"b"}
> },
> "delete-requesthandler" :"/mypath"
> }'
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org