[
https://issues.apache.org/jira/browse/SOLR-13936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16992107#comment-16992107
]
Noble Paul commented on SOLR-13936:
-----------------------------------
bq. would the /api/cluster sibling have weaker or different error messages?
Yes and no. Yes, it would fail to load the core itself. but it won't recover.
This will actually bring the collection down
That validation is less useful. We just fail to load the core if there is a
post-loading failure.
validations are done against
* validity of data itself
* validity of classes .e.g: does the class exist and if the class implement
the right interfaces and if it can be loaded
We could do these irrespective of the core being present or not.
{quote}After a collection is created on the configset, both endpoints would
manipulate exactly the same data, which is super confusing:
{quote}
which collection? In case of a shared configset, you have no fixed collection
to work with. Collections may come and go.
> 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]
