[
https://issues.apache.org/jira/browse/IGNITE-10896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16755801#comment-16755801
]
Artem Budnikov commented on IGNITE-10896:
-----------------------------------------
The behaviour that [~ARomantsov] suggests for the two options should be
extended to all three options. It'll be better if all three options can be used
simultaneously. Mutually exclusive filtering options are really confusing.
This is how I envision it:
The default value for `--exclude-caches` is an empty set.
The default value for `--cache-filter` is no filtering.
The default value for `\-\-caches` is all caches.
All three options can be used simultaneously or all three can be omitted (in
which case the default values are used). If the result of applying the options
is an empty set, the script should print a warning to the console.
> Add ability to use simultaneous cache filtering options with control.sh
> --cache idle_verify
> -------------------------------------------------------------------------------------------
>
> Key: IGNITE-10896
> URL: https://issues.apache.org/jira/browse/IGNITE-10896
> Project: Ignite
> Issue Type: Improvement
> Reporter: ARomantsov
> Priority: Major
> Fix For: 2.8
>
>
> Now I can use only one of next options
> 1) --exclude-caches cache1,...,cacheN
> 2) --cache-filter ALL|SYSTEM|PERSISTENT|NOT_PERSISTENT
> 3) cache1,...,cacheN
> Trying to use two or more of this options currently results in error:
> {noformat}
> Error: Should use only one of option: --excludeCaches, --cache-filter or pass
> caches explicitly
> {noformat}
> Instead, utility should do the following:
> 1) when two or more options specified, result cache set to make dump of
> should be logical AND of results of each option applied individually.
> ex.
> {noformat}
> cache.* --cache-filter PERSISTENT
> {noformat}
> should select all persistent caches starting from 'cache'
> {noformat}
> --cache-filter ALL
> --exclude-caches wrong-.*-caches
> {noformat}
> should select all caches but matching 'wrong-.*-caches' regexp
> etc.
> 2) filtering options passed to control utility should be logged into result
> dump file, so that user could understand that dump was taken from subset of
> cluster caches
> 3) when result of filter or filters AND'ing is empty set of cache names,
> proper error message should be given and no dump file generated.
> e.g.
> {noformat}Error: can't find any cache matching cache names '--skup-zerus' and
> cache filter 'PERSISTENT', dump won't be generated.{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
