[
https://issues.apache.org/jira/browse/SOLR-17862?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18014494#comment-18014494
]
David Smiley commented on SOLR-17862:
-------------------------------------
I think the safest step would be to limit the config API to only manipulate an
"AUTOCREATED" configSet, which is basically a configSet private to a
collection. Also see my recent wish-list JIRA: SOLR-17817 which is related.
> Config API is not per-collection; applies to all collections using the same
> configset
> -------------------------------------------------------------------------------------
>
> Key: SOLR-17862
> URL: https://issues.apache.org/jira/browse/SOLR-17862
> Project: Solr
> Issue Type: Bug
> Reporter: Chris M. Hostetter
> Priority: Major
>
> The "Config API" uses a URL path prefix of
> {{/api/collections/<<COLLECTION_NAME>>/config}} and [has documentation that
> says|https://solr.apache.org/guide/solr/latest/configuration-guide/config-api.html]...
> {quote}
> All Config API endpoints are collection-specific, meaning this API can
> inspect or modify the configuration for a single collection at a time.
> {quote}
> ...but this is a lie. Using the Config API to modify any aspect of a
> collection actually modifies the {{configoverlay.json}} in the configset, and
> impacts all collections using that configset.
> ----
> * The "Config API" should be changed to use some new a URL path prefix that
> is specific to the name of the configset (Example:
> {{/api/configset-props/<<CONFIGSET_NAME>>/}})
> * The Existing {{/api/collections/<<COLLECTION_NAME>>/config}} URL should be
> deprecated
> * Documentation should be updated accordingly
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
