Can't get to JIRA right now, but the Collections API MODIFYCOLLECTION seems right for adding properties
On Tue, Dec 12, 2017 at 10:58 AM, Shawn Heisey (JIRA) <j...@apache.org> wrote: > Shawn Heisey created SOLR-11751: > ----------------------------------- > > Summary: 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 > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
