[
https://issues.apache.org/jira/browse/SOLR-9268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15366363#comment-15366363
]
Varun Thacker commented on SOLR-9268:
-------------------------------------
For cluster level features I am of the opinion that we should have specific
endpoints per feature.
For example basic auth has APIs to manage roles / users etc on a dedicated
endpoint ( /solr/admin/authentication )
https://cwiki.apache.org/confluence/display/solr/Basic+Authentication+Plugin
Similarly we should have an endpoint for backup repositories (
solr/admin/backup_repository ) where we can define the repositories and modify
them dynamically.
If we have one endpoint I feel it gets messy. Imagine if security / backup
repository both could be configured via one endpoint (
/solr/admin/cluster_property ) , each with it's own json payload
> Support adding/updating backup repository configurations 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
> Attachments: SOLR-9268.patch
>
>
> 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]
