[
https://issues.apache.org/jira/browse/SOLR-8299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15008308#comment-15008308
]
Shai Erera commented on SOLR-8299:
----------------------------------
bq. I thought about that too, but just wanted to be sure that I'm not
overlooking any multi-tenant security requirement.
Yes, that's a good point, but at the moment I think that whoever will hit this
message, will have no idea what collection uses the config. Also, if we want to
address multi-tenant and security stuff, I think that the app should be able to
handle that. Maybe if we return a proper error code, or throw a specific
exception. Since Solr does not support multi-tenancy natively, I don't think
that we should try to protect it.
> 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: [email protected]
For additional commands, e-mail: [email protected]
