You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Shai Erera (JIRA)" <ji...@apache.org> on 2015/11/16 22:18:11 UTC
[jira] [Commented] (SOLR-8299) ConfigSet DELETE should not allow
deletion of a a configset that's currently being used
[ https://issues.apache.org/jira/browse/SOLR-8299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15007340#comment-15007340 ]
Shai Erera commented on SOLR-8299:
----------------------------------
bq. "Can not delete ConfigSet as it is being used by another collection"
I would add the collection name to the message to make it more helpful?
bq. I've allowed deletion of configset when force=true, but I really believe we shouldn't allow that.
I tend to agree with you on that. The problem is, from what I've seen, that the collection becomes unusable after you delete its configuration, even if it's later restored. Perhaps it was a point-in-time behavior of the code and has been fixed since then, but I prefer that we don't allow forcing the deletion of a configuration.
Why would a user want to force-delete a configuration, when there are collections that use it? What good comes out of it? Perhaps we should add this 'force' support after we see an actual use case?
> ConfigSet DELETE should not allow deletion of a a configset that's currently being used
> ---------------------------------------------------------------------------------------
>
> Key: SOLR-8299
> URL: https://issues.apache.org/jira/browse/SOLR-8299
> Project: Solr
> Issue Type: Bug
> Reporter: Anshum Gupta
> Assignee: Anshum Gupta
> Attachments: SOLR-8299.patch
>
>
> The ConfigSet DELETE API currently doesn't check if the configuration directory being deleted is being used by an active Collection. We should add a check for the same.
--
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