[
https://issues.apache.org/jira/browse/SOLR-8299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15007372#comment-15007372
]
Anshum Gupta commented on SOLR-8299:
------------------------------------
Thanks Shai.
bq. I would add the collection name to the message to make it more helpful?
I thought about that too, but just wanted to be sure that I'm not overlooking
any multi-tenant security requirement.
bq. 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?
I completely agree with that but again, wanted to be sure that I was not
missing a use-case here. Also, the collection does stay in an unusable state
once you delete the config that's in-use and a ton of errors get logged too.
But I'm now more convinced to make both of those changes before I commit.
> 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-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
