[
https://issues.apache.org/jira/browse/SOLR-11751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16288106#comment-16288106
]
Erick Erickson commented on SOLR-11751:
---------------------------------------
The collecitons API MODIFYCOLLECTION can add/modify collection properties I
think, which would allow you to add the tags at least already. We'd need to
build in code to respect such tags of course.
I'd guess you'd have to change the property in order to be able to delete the
collection if you _really_ wanted to delete it at some later point.
I can imagine you'd like to lock down configsets too, although that'd be a
sticky wicket wrt field guessing, and the schema and config APIs.
> Collections API: Implement collection properties that block Collections API
> actions
> ------------------------------------------------------------------------------------
>
> Key: SOLR-11751
> URL: https://issues.apache.org/jira/browse/SOLR-11751
> Project: Solr
> Issue Type: New Feature
> Security Level: Public(Default Security Level. Issues are Public)
> Components: SolrCloud
> Affects Versions: 7.1
> Reporter: Shawn Heisey
> Priority: Minor
>
> [~yriveiro] asked on the mailing list whether we had any ability to prevent a
> collection from being deleted with a property.
> I don't know of any way to do this currently, but it does strike me as
> useful, so here's the proposal:
> Implement some new collection properties, that when set, block certain
> Collections API actions.
> At this time, I'm not even sure that user-modifiable collection-level
> properties actually exist, so that may need to be implemented before this can
> be implemented. It *could* be done with cluster properties, but that seems
> like a hack.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
