You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Anshum Gupta (JIRA)" <ji...@apache.org> on 2014/09/26 00:56:34 UTC
[jira] [Commented] (SOLR-6278) add
admin/collections?action=DELETEREPLICA&core=... support, make
collection=... and shard=... parameters optional
[ https://issues.apache.org/jira/browse/SOLR-6278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14148447#comment-14148447 ]
Anshum Gupta commented on SOLR-6278:
------------------------------------
Ideally, we should move away from anything 'core' level exposed at the public API level.
All calls should involve Collection/Shard/Replica instead. With this support we'd just be making it tougher to move away from how things are done right now.
>From my knowledge, the exposure of Core level details was because this is how it was made to have something up and running e.g. create a core with name collection1 to create a collection1.
> add admin/collections?action=DELETEREPLICA&core=... support, make collection=... and shard=... parameters optional
> ------------------------------------------------------------------------------------------------------------------
>
> Key: SOLR-6278
> URL: https://issues.apache.org/jira/browse/SOLR-6278
> Project: Solr
> Issue Type: Improvement
> Reporter: Christine Poerschke
> Assignee: Erick Erickson
> Attachments: SOLR-6278.patch
>
>
> To add {{core=...}} as an alternative to {{replica=...}} way of identifying what is to be deleted, {{collection=...}} and {{shard=...}} to be optional provided the other parameters uniquely identify exactly one deletion target.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org