[
https://issues.apache.org/jira/browse/SOLR-6607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14228635#comment-14228635
]
Noble Paul commented on SOLR-6607:
----------------------------------
how about adding extra information to the {{/config}} end point
example
{code}
"/analysis/field": {
"_meta_" : {
"source" : "overlay", // alternatively, implicit,
solrconfig.xml
"overrides" : " solrconfig.xml"
}
"startup": "lazy",
"name": "/analysis/field",
"class": "solr.FieldAnalysisRequestHandler"
}
{code}
> 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
> Fix For: 5.0, Trunk
>
> 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-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
