[
https://issues.apache.org/jira/browse/CASSANDRA-7622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16448475#comment-16448475
]
Chris Lohfink commented on CASSANDRA-7622:
------------------------------------------
I think theres 2 things here
# blanket table exposing ALL metrics (so that jmx isnt required)
# provide a good ux for exploring them
I think for #1 we still need a table like the one in patch, otherwise every
time a metric is added a curated table would also need to be updated which
might be prohibitive for 1 off metrics that while critical in some scenarios
are so off the normal path that it would be wasted effort and overwhelming.
For #2 I was thinking of basically having an equivalent of the nodetool views++
(tablestats, tablehistograms, info, netstats, clientlist etc but also some new
things), but that needs to be broken into sub tasks since working on it until
the mechanism for making them is nailed down is kinda waste of time.
> Implement virtual tables
> ------------------------
>
> Key: CASSANDRA-7622
> URL: https://issues.apache.org/jira/browse/CASSANDRA-7622
> Project: Cassandra
> Issue Type: Improvement
> Components: CQL
> Reporter: Tupshin Harper
> Assignee: Chris Lohfink
> Priority: Major
> Fix For: 4.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
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
