[
https://issues.apache.org/jira/browse/CASSANDRA-7622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16448357#comment-16448357
]
Benjamin Lerer commented on CASSANDRA-7622:
-------------------------------------------
{quote}table metrics (all of them)
{quote}
The schema of this table could be much better in my opinion. The user needs to
know what metric type is corresponding to the metric he is looking at to be
able to fetch only the columns that are meaningful for that metric. Otherwise
he will just get a bunch of {{NULL}} values. {{Gauge}} value are simply
returned as {{TEXT}} which prevent you to do arithmetic operations or
aggregation if you want to. As an admin I would expect a more powerful schema.
When I am mentioning all metrics I am refering to all the C* metrics. Streaming
metrics, Cache metrics ... all of them should be exposed in the best possible
way for an admin.
> 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: [email protected]
For additional commands, e-mail: [email protected]
