[
https://issues.apache.org/jira/browse/CASSANDRA-7622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15320710#comment-15320710
]
Sylvain Lebresne commented on CASSANDRA-7622:
---------------------------------------------
bq. referring to this as "Exposing jmx via cql"
That's a slight simplification, we're more talking here of exposing _metrics_
through CQL. We are, in particular, not at all talking about using some mbeans
in any way. We could, maybe, create a custom Reporter to do this, I hadn't
considered this, and that would have some convenience, but the other solution
is just to manually register each existing metrics through whatever solution we
come up with here. The advantage of the latter, manual solution is that we'll
probably have more control on how the actual (virtual) tables look like, which
I personally like (we'd be trading a bit of manual labor for a better user
experience, which I'd say is a fair trade-off), but certainly happy to consider
the other options.
> 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)
