[
https://issues.apache.org/jira/browse/CASSANDRA-7622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15320714#comment-15320714
]
Aleksey Yeschenko commented on CASSANDRA-7622:
----------------------------------------------
Initially the ticket was about exposing configuration over CQL, not metrics.
FWIW I'm not convinced that exposing all metrics over virtual tables even makes
sense.
bq. Yes please to scoping for read-only. Also, SHOW VARIABLES would be a cause
for celebration and cheer among our community of operations folks (would not
even care about filtering for first a first version either, just that we could
get it).
Yes to both. Let's start with {{SHOW VARIABLES}} and go from there.
> 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)
