[
https://issues.apache.org/jira/browse/SOLR-13936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16990141#comment-16990141
]
Noble Paul commented on SOLR-13936:
-----------------------------------
{quote}Glad to hear it, but clearly I missed the discussion. Where can I find
it?
{quote}
It was in slack. We were having a discussion with [~dsmiley] . I don't remember
which channel exactly.
But the point is, that is the logical place where you should have that API. We
have to have end points that make sense. Either we keep a configset as part of
a collection, in that case there is no need to have direct access to configset.
If the configset is separate, then it should have its own end point
{quote}If you want the ability to upload a config and then modify it before
it's ever used, couldn't you just do the edits locally and upload the configset
the way you actually intend to use it?
{quote}
Yes, you can upload a configset. But, that argument works for the entire config
+ schema API.
Probably you should look at the tickets that introduced config API , Schema
API. We discussed at length why these are required
> 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]
