[
https://issues.apache.org/jira/browse/SOLR-13553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16876932#comment-16876932
]
Noble Paul commented on SOLR-13553:
-----------------------------------
Loading an arbitrary handler with arbitrary parameters is the whole point of
this ticket, right?
The security is to be enforced at the lib loading point. If the class is
available in the classpath, you can register it using a config API today. The
only difference here is, you can register it at a node level instead at a
collection level
You can delete a handler and add it back. Isn't that obvious?
> Node level custom RequestHandlers
> ---------------------------------
>
> Key: SOLR-13553
> URL: https://issues.apache.org/jira/browse/SOLR-13553
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Noble Paul
> Assignee: Noble Paul
> Priority: Major
>
> These components
> * Available on every node
> * deployed at the {{CoreContainer}} level
> * Available at {{/solr/admin/<plugin-name> or {{/api/node/<plugin-name>}}
> (v2 style)
> * Should implement the {{SolrRequestHandler}} interface
> The configuration is persisted in {{clusterprops.json}}
> {code}
> curl -X POST -H 'Content-type:application/json' --data-binary '{
> "add-requesthandler": {
> "name": "/foo",
> "class" : "fully.qualified.ClassName"
>
> }
> }' http://localhost:8983/api/cluster
> {code}
> delete it using
> {code}
> curl -X POST -H 'Content-type:application/json' --data-binary '{
> "delete-requesthandler": "/foo"
> }' http://localhost:8983/api/cluster
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
