[
https://issues.apache.org/jira/browse/CASSANDRA-7622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15320846#comment-15320846
]
Brian Hess commented on CASSANDRA-7622:
----------------------------------------
I'm still curious how you would get the JMX values (SHOW VARIABLES or whatever)
for a particular node. That is, how would this look syntactically (WHERE
clause? Special CQL?)? And if it's something like a WHERE clause, then how will
the driver route the query correctly? Would it be through a custom
LoadBalancingPolicy? If so, then it could be hard to mix normal CQL with these
(as you'd want a different LBP for the normal CQL queries).
> 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)
