[jira] [Assigned] (CASSANDRA-4063) Expose nodetool cfhistograms for secondary index CFs

["Jonathan Ellis (Assigned) (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CASSANDRA-4063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jonathan Ellis reassigned CASSANDRA-4063:
-----------------------------------------

    Assignee: Brandon Williams

At worst we should be able to use our schema knowledge to know if we should query with ICF or CF type.
                
> Expose nodetool cfhistograms for secondary index CFs
> ----------------------------------------------------
>
>                 Key: CASSANDRA-4063
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-4063
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Tools
>            Reporter: Tyler Hobbs
>            Assignee: Brandon Williams
>            Priority: Minor
>              Labels: jmx
>
> With the ObjectName that NodeProbe uses, the JMX query can only match mbeans with type "ColumnFamilies".  Secondary index CFs have a type of "IndexColumnFamilies", so the query won't match them.
> The [ObjectName documentation|http://docs.oracle.com/javase/6/docs/api/javax/management/ObjectName.html] indicates that you can use wildcards, which would be the perfect solution if it actually worked.  I'm not sure if it's some quoted vs non-quoted pattern issue, or if it's particular to the {{newMBeanProxy()}} method, but I could not get wildcards to match the secondary index CFs.  Explicitly setting the "type" field to "IndexColumnFamilies" did work.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira