[
https://issues.apache.org/jira/browse/SOLR-9268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15358998#comment-15358998
]
Varun Thacker commented on SOLR-9268:
-------------------------------------
The cluster prop API
(https://cwiki.apache.org/confluence/display/solr/Collections+API#CollectionsAPI-api11)
supports simple key value pairs.
Let's take the backup/restore repository interface for example - Right now we
put the configurations in solr.xml file as that was the only place fit.
So the discussion came about having better support and hence have APIs for
solr.xml . But I agree what we really want is better API support in general. It
doesn't need to be exposed as solr.xml . In fact we should't latch on to that
and add more stuff . But the motivation remains the same.
One approach is to have a specific endpoint for backup/restore and that gets
stored internally as a {{reporitory.json}} file.
The other approach is have a generic cluster property API which can deal with
nested schemas.
> Support updating configuration in solr.xml via API
> --------------------------------------------------
>
> Key: SOLR-9268
> URL: https://issues.apache.org/jira/browse/SOLR-9268
> Project: Solr
> Issue Type: New Feature
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Hrishikesh Gadre
>
> Currently users need to manually modify solr.xml in Zookeeper to update the
> configuration parameters (and restart Solr cluster). This is not quite user
> friendly. We should provide an API to update this configuration. (This came
> up during the discussions in SOLR-9242).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
