[
https://issues.apache.org/jira/browse/SOLR-11751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16288156#comment-16288156
]
Shawn Heisey commented on SOLR-11751:
-------------------------------------
[~erickerickson], I didn't see your comment until after I had finished adding
my optional ideas. Which I did type immediately, but forgot to click "Add"
until later.
Regarding the optional idea where an override parameter must match the value in
the property: If we make it so that an empty string in the property can't ever
be matched, that would allow somebody to easily prevent the override. Of
course the same thing could be accomplished with a special string, like
"NO_OVERRIDE".
> 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]
