[
https://issues.apache.org/jira/browse/SOLR-17862?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18018645#comment-18018645
]
Christos Malliaridis commented on SOLR-17862:
---------------------------------------------
Based on my understanding of Solr's resources
- a configset is a standalone resource that is only referenced / used by
collections
- a one to many relationship exists here, one configset can have many
collections
- a configset can exist without a collection, but
- a collection cannot exist without a configset
So the API endpoint (following REST practices)
/collections/:collectionName/config doesn't make sense if it is a reference to
a configset (at least from the relationship perspective), because modifying for
example is not impacting a single collection only. It should rather be
/configsets/:configName and consumers should only get basic information /
details from /collections/:collectionName/config (only HTTP GET should be
allowed).
Additionally, if /collections/:collectionName/config is not the configset but
the collection configuration (different resource), then all operations would
make sense, as long as they are applied to the :collectionName only.
> 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]
