[
https://issues.apache.org/jira/browse/SOLR-13936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16991027#comment-16991027
]
Noble Paul commented on SOLR-13936:
-----------------------------------
[~janhoy]
There are 2 different types of users.
* Users who just create collections without bothering about the configset
* Users who have multiple collections with shared configset. These are power
users who know very well about a configset
Both are valid usecases. I do not wish to sacrifice one over the other.
bq. I'm not happy with just simply adding more API surface without taking
anything away.
The APIs are same. But they apply differently. If you look at the PR, both the
features are using the same code. Yes, there is a lot of cruft I would like to
get rid of. I disagree with the idea that we can't add something unless we
remove something.
We should go thorough Solr APIs through a fine toothed comb and ask these
questions
* Is this useful? Is it worth keeping it around?
* Is it logical? does it need change
> 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]
