[
https://issues.apache.org/jira/browse/CASSANDRA-3527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13157364#comment-13157364
]
Kelley Reynolds commented on CASSANDRA-3527:
--------------------------------------------
bq. It's two very different types of data, that serve very different purposes.
I think it's a bug to have multiple ways of getting and setting values,
especially since the line between JMX/Thrift/ is already. Some examples: You
can specify strategy and RF when creating a keyspace with CQL but you can't
change it. You specify the compaction settings for a column family but you
can't compact it. You can set the key_ and row_cache settings for a column
family on creation but you have to update it through nodetool. You can describe
the ring but not not show it's common stats like are show through nodetool info
.. and you can't do it with CQL, only with Thrift except you can get some of it
through the system keyspace which may or may not be desirable in the first
place, etc.
Claiming different data types makes no sense to me, and I don't see a clear
delineation of data access and configuration and administration either. It
looks inertial, and I think consolidating and clarifying it would be an
improvement.
> Expose JMX values via CQL interface
> -----------------------------------
>
> Key: CASSANDRA-3527
> URL: https://issues.apache.org/jira/browse/CASSANDRA-3527
> Project: Cassandra
> Issue Type: New Feature
> Components: Core
> Reporter: Kelley Reynolds
> Priority: Minor
> Labels: cql
>
--
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
