[
https://issues.apache.org/jira/browse/CASSANDRA-4191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lyuben Todorov updated CASSANDRA-4191:
--------------------------------------
Comment: was deleted
(was: So, from the comments I gather that we want to have a list of ks' and cfs
in the style of:
{code:xml}
nodetool cfstats ks1.cf1 ks1.cf2 ks2
{code}
The default being to include all these keyspaces/cfs, with the ability to
supply an -i flag meaning ignore only these keyspaces/cfs and display
everything else. Or would it be better to go with the 2 flag aproach where
users supply something like:
{code:xml}
nodetool cfstats -i ks1.cf1 ks1.cf2 -e ks2
{code}
where we include everything after -i and ignore everything after -e
[~dbrosius] [~jbellis] What do you think?)
> Add `nodetool cfstats <ks> <cf>` abilities
> ------------------------------------------
>
> Key: CASSANDRA-4191
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4191
> Project: Cassandra
> Issue Type: New Feature
> Affects Versions: 1.2.0 beta 1
> Reporter: Joaquin Casares
> Assignee: Lyuben Todorov
> Priority: Minor
> Labels: datastax_qa
> Fix For: 1.2.9
>
> Attachments: 4191.patch, 4191_specific_cfstats.diff
>
>
> This way cfstats will only print information per keyspace/column family
> combinations.
> Another related proposal as an alternative to this ticket:
> Allow for `nodetool cfstats` to use --excludes or --includes to accept
> keyspace and column family arguments.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
