[
https://issues.apache.org/jira/browse/SOLR-13936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16992013#comment-16992013
]
Jan Høydahl commented on SOLR-13936:
------------------------------------
The only need for this would be BEFORE you create a collection. After a
collection is created on the configset, both endpoints would manipulate exactly
the same data, which is super confusing:
{code:java}
/api/cluster/configset/<config-name>/config
/api/collection/<collection-name>/config
{code}
Question: How would various validation work for a core-less config-set? I was
under the impression that e.g. a call to the Schema REST api for a collection
caused a core reload and thus you would get notified on errors. But if there is
no backing core, would the /api/cluster sibling have weaker or different error
messages? (Have not checked code)
> 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]
