[
https://issues.apache.org/jira/browse/SOLR-13553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16876900#comment-16876900
]
Andrzej Bialecki commented on SOLR-13553:
------------------------------------------
The delete op is just a convenience because {{clusterprops.json}} is editable
via other means, too - and this has some security implications: you can then
load an arbitrary handler with arbitrary parameters.
bq. The delete operation is there just for sake of completeness
Quite the opposite - it's strange to be able to delete a handler without being
able to add it back or modify.
> 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]
