[
https://issues.apache.org/jira/browse/SOLR-6278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Erick Erickson resolved SOLR-6278.
----------------------------------
Resolution: Won't Fix
See discussion. There's still room for being able to do node-type operations,
think of a physical machine going down and you want to remove all traces of it
from the cluster state, but that's for another ticket.
> 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: [email protected]
For additional commands, e-mail: [email protected]
