[
https://issues.apache.org/jira/browse/SOLR-13936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16991832#comment-16991832
]
Ishan Chattopadhyaya commented on SOLR-13936:
---------------------------------------------
As for taking this forward, I envision this configset based config/schema API
be released in 8x, and be marked experimental. In 9x, we move the collection
based config/schema API to /api/cluster endpoint. Also, unmark the experimental
annotation on this. As Jan mentioned, the reference guide post for this issue
should provide a clear idea on how we position this for our users.
bq. What is the target release for this change? Jira doesn't say.
We don't have a field for that. Fix version is usually added at the time of
commit/merge/push.
bq. I think these questions are not out of scope of this issue.
[~apoorvprecisely], WDYT?
bq. it doesn't really address the underlying inconsistency of how the
configsets are used
Can you please open a JIRA about those inconsistencies and we can discuss about
tackling them there?
> 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]
