[
https://issues.apache.org/jira/browse/SOLR-13936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16990999#comment-16990999
]
Noble Paul commented on SOLR-13936:
-----------------------------------
bq. I think the old collection level config API should be moved to the
/api/cluster level,
I'm not sure if it is intuitive.
As Ishan said, it is not intuitive for most users if we eliminate the config
APIs from collection level.
Ideally, a casual user should do the following
# create a collection (without specifying a configset). Solr automatically
creates a configset
# add schema fields or manipulate config through {{<collection-name>/config}}
and {{<collection-name>/schema}}
This class of users will not or should not know about a configset
There are extra functionalities for READ apis done through collection as a live
collection is available. For instance, if a plugin is loaded from a package,
the API tells you if it is indeed loaded from a package
> Schema/Config endpoints to modify configset with no core/collection
> -------------------------------------------------------------------
>
> Key: SOLR-13936
> URL: https://issues.apache.org/jira/browse/SOLR-13936
> Project: Solr
> Issue Type: New Feature
> Security Level: Public(Default Security Level. Issues are Public)
> Components: config-api
> Reporter: Apoorv Bhawsar
> Priority: Minor
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> All schema/config configurations should work even in cases where a collection
> is not associated with them
> This jira will involve
> 1. Refactoring existing handler/manager to work without {{SolrCore}}
> 2. Adding {{/api/cluster}} endpoints to support such modifications
> Endpoints -
> * {{/api/cluster/configset/\{name}/schema}}
> * {{/ap/cluster/configset/\{name}/config}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
