[
https://issues.apache.org/jira/browse/SOLR-7124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14340205#comment-14340205
]
Shawn Heisey commented on SOLR-7124:
------------------------------------
bq. We should also keep in mind that a user can replace existing configs for a
collection and call collection RELOAD. So adding this check can prevent one
from easily replacing configs. Thoughts?
The check to see whether the config is in use would only be required on
delconfig. It would not be required on upconfig, because upconfig will not
delete any files from an existing config, it will only add or overwrite.
A slightly different check (making sure the config actually exists) *might*
need to be performed for linkconfig. I know it is possible to link a config to
a collection that doesn't exist yet, so that when it is created it will already
have the correct config. it is probably also possible to make that link to a
config that doesn't exist, but I think we should prevent that.
> Add "delconfig" command to zkcli
> --------------------------------
>
> Key: SOLR-7124
> URL: https://issues.apache.org/jira/browse/SOLR-7124
> Project: Solr
> Issue Type: New Feature
> Components: SolrCloud
> Affects Versions: 5.0
> Reporter: Shawn Heisey
> Priority: Minor
> Fix For: 5.1
>
>
> As far as I know, there is no functionality included with Solr that can
> delete a SolrCloud config in zookeeper.
> A "delconfig" command should be added to ZkCli and the zkcli script that can
> accomplish this. It should refuse to delete a config that is in use by any
> current collection.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
