[
https://issues.apache.org/jira/browse/SOLR-13273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ishan Chattopadhyaya updated SOLR-13273:
----------------------------------------
Fix Version/s: (was: 8.1)
8.2
> Add a collection selector to policy rules
> -----------------------------------------
>
> Key: SOLR-13273
> URL: https://issues.apache.org/jira/browse/SOLR-13273
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Components: AutoScaling
> Reporter: Shalin Shekhar Mangar
> Priority: Major
> Fix For: master (9.0), 8.2
>
>
> Today, we must specify the exact collection name on which a policy rule is
> applied or omit it entirely in which case the rule matches all collections.
> In case a rule must apply to a subset of collections, before we create a new
> collection, we must copy over the rule with the collection name changed to
> the new collection.
> It'd be nice to have a selector for collections based on the collection
> property.
> For example:
> {code}
> {"replica": "#ALL", "collection":{"property_name":"property_value"},
> "sysprop.node_type": "xyz"}
> {code}
> The above rule matches all collections which have {{property_name}} set to
> {{property_value}} as a collection property. This makes it possible to add
> just one rule and have it apply to all collections having the property.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
