[
https://issues.apache.org/jira/browse/SOLR-13936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16992009#comment-16992009
]
Noble Paul edited comment on SOLR-13936 at 12/9/19 10:47 PM:
-------------------------------------------------------------
{quote}should we rather focus on designing a single consistent API, in which
case this one will probably need to be removed or substantially modified?
{quote}
The point is , there is no consensus on
* if this is inconsistent
* What will that alternate design look like?
My understanding is the following
* Normal users do not need to know about a configset and they would access
everything through the collection. The workflow would be create a collection,
invoke APIs to modify the config
* Power users would want to share configsets. They will use the configset API
to edit config
The API is exactly the same, the code that is executed is exactly the same. The
only difference is, one is invoked on
{{/solr/<collection-name>/<schema|config>}} and the other is invoked at
{{/api/cluster/configset/<schema|config>}}. I see no reason for ambiguity
was (Author: noble.paul):
{quote}should we rather focus on designing a single consistent API, in which
case this one will probably need to be removed or substantially modified?
{quote}
The point is , there is no consensus on
* if this is inconsistent
* What will that alternate design look like?
My understanding is the following
* Normal users do not need to know about a configset and they would access
everything through the collection. The workflow would be create a collection,
invoke APIs to modify the config
* Power users would want to share configsets. They will use the configset API
to edit config
The API is exactly the same, the code that sis executed is exactly the same.
The only difference is one is invoked on
{{/solr/<collection-name>/<schema|config>}} and the other is invoked at
{{/api/cluster/configset/<schema|config>}}. I see no reason for ambiguity
> 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]
