[
https://issues.apache.org/jira/browse/SOLR-11751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16288137#comment-16288137
]
Shawn Heisey commented on SOLR-11751:
-------------------------------------
Optional ideas:
* If a blocking property can have an arbitrary value, implement an API
parameter that would override the block, IF the value for that parameter
matches the value in the property.
* One single property that blocks ALL Collections API usage.
A tangent idea, for a separate issue:
* Prevent external CoreAdmin requests on SolrCloud unless a property is set
that essentially makes the user declare "yes, I know what I'm doing". This one
probably should work at the cluster or collection level.
> 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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
