[
https://issues.apache.org/jira/browse/SOLR-13936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16990924#comment-16990924
]
Ishan Chattopadhyaya commented on SOLR-13936:
---------------------------------------------
bq. Should not the old config-api and schema-api be deprecated too if we move
both of them to the cluster level?
I think the old collection level config API should be moved to the /api/cluster
level, but it should continue to work (maybe using same code paths under the
covers). I think regular users will prefer to use it because no Solr user
should need to be aware of the concept of the configsets. The default configset
was a step in that direction. I'm against deprecating the collection level APIs
for doing this. It would be *absolutely terrible* if a user created collection
"mycollection", but had to invoke config API on
`/api/cluster/configset/mycollection.AUTOCREATED`. (A user would be left
wondering, what is a "configset" and why this "AUTOCREATED" suffix etc.).
However, sorry [~apoorvprecisely], for taking this issue in a tangent. This
issue shouldn't be about what we do with the collection level config APIs.
> 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]
