You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@lucene.apache.org by GitBox <gi...@apache.org> on 2020/05/18 08:02:40 UTC

[GitHub] [lucene-solr] shalinmangar commented on a change in pull request #1512: SOLR-13325: Add a collection selector to ComputePlanAction

shalinmangar commented on a change in pull request #1512:
URL: https://github.com/apache/lucene-solr/pull/1512#discussion_r426437892



##########
File path: solr/solr-ref-guide/src/solrcloud-autoscaling-trigger-actions.adoc
##########
@@ -29,12 +29,13 @@ commands which can re-balance the cluster in response to trigger events.
 The following parameters are configurable:
 
 `collections`::
-A comma-separated list of collection names. If this list is not empty then
-the computed operations will only calculate collection operations that affect
-listed collections and ignore any other collection operations for collections
+A comma-separated list of collection names. This can also be a selector on the collection property e.g. `collections: {'policy': 'my_custom_policy'}` will match all collections which use the policy named `my_customer_policy`.

Review comment:
       Thanks. I expanded the description a bit. I added another example that I am not really happy with -- I cannot think of a use-case where something other than policy might be useful especially given the fact that values must match exactly. Suggestions welcome.




----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org