[
https://issues.apache.org/jira/browse/CASSANDRA-7622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16452667#comment-16452667
]
Chris Lohfink edited comment on CASSANDRA-7622 at 4/25/18 5:19 PM:
-------------------------------------------------------------------
I don't think I see the benefit to that schema, you have to have a schema
change or dynamic schema for whenever a new metric is added? Reminder there
have been cases where metrics dont appear until execution (not currently but in
past), so its not unheard of for the metric set to change at runtime. And
requiring {{EXPAND ON;}} to explore what metrics exist I think would be a high
bar for a lot of people who don't even know the command exists, which is also
session wide not just for the query.
was (Author: cnlwsu):
I don't think I see the benefit to that schema, you have to have a schema
change or dynamic schema for whenever a new metric is added? And requiring
{{EXPAND ON;}} to explore what metrics exist I think would be a high bar for a
lot of people who don't even know the command exists, which is also session
wide not just for the query.
> 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
