[ https://issues.apache.org/jira/browse/CASSANDRA-7622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15319968#comment-15319968 ]
Chris Lohfink commented on CASSANDRA-7622: ------------------------------------------ May be out of scope of this ticket, but I get nervous when continually referring to this as "Exposing jmx via cql". Are we referring to creating a new Reporter for the CassandraMetricsRegistry so all metrics just automagically are exposed or are we talking about using {{ManagementFactory.getPlatformMBeanServer()}} and actually reading the mbeans, having manual process of updating a list of exposed data? > Implement virtual tables > ------------------------ > > Key: CASSANDRA-7622 > URL: https://issues.apache.org/jira/browse/CASSANDRA-7622 > Project: Cassandra > Issue Type: Improvement > Reporter: Tupshin Harper > Assignee: Jeff Jirsa > Fix For: 3.x > > > There are a variety of reasons to want virtual tables, which would be any > table that would be backed by an API, rather than data explicitly managed and > stored as sstables. > One possible use case would be to expose JMX data through CQL as a > resurrection of CASSANDRA-3527. > Another is a more general framework to implement the ability to expose yaml > configuration information. So it would be an alternate approach to > CASSANDRA-7370. > A possible implementation would be in terms of CASSANDRA-7443, but I am not > presupposing. -- This message was sent by Atlassian JIRA (v6.3.4#6332)