[ 
https://issues.apache.org/jira/browse/SOLR-13936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16991814#comment-16991814
 ] 

Andrzej Bialecki commented on SOLR-13936:
-----------------------------------------

What is the target release for this change? Jira doesn't say.
 * if it's 9.0 only then we should do this properly - consider the use cases 
and figure out a design that presents a minimal and consistent API, and we 
should feel free to break back-compat when necessary.
 * if it's 8x then I agree with Jan and Jason that even though it feels like a 
convenience it still long-term adds a maintenance burden and a point of 
confusion, because it doesn't really address the underlying inconsistency of 
how the configsets are used. Are we then supposed to carry this API over to 
9.0? Or, as explained above, should we rather focus on designing a single 
consistent API, in which case this one will probably need to be removed or 
substantially modified?

I think these questions are not out of scope of this issue.
{quote}+1 to deprecate current configSet manipulation that are coupled to the 
collection.  It's confusing/weird.
{quote}
Deprecation makes sense if you propose something better and more consistent. 
However, this new API is not it, because the underlying model of how configset 
templates are used still remains inconsistent, and this API only tries to work 
around the broken model.

> 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]

Reply via email to