[
https://issues.apache.org/jira/browse/CASSANDRA-7622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14074602#comment-14074602
]
Robert Stupp commented on CASSANDRA-7622:
-----------------------------------------
So there would be two kinds of "vTables"? One that is consistent over all nodes
(e.g. cluster status) and one that has node-dependent values (e.g.
configuration per node)? I'm not against this one (it's great to have vTables)
- but for example querying information from all nodes could be very expensive
large clusters (1000 nodes) - the coordinater would have to query all 1000
cluster nodes. I guess that [~hayato.shimizu] had something like {{SELECT
DISTINCT seed_nodes FROM node_config}} in mind to find configuration mistakes.
> Implement virtual tables
> ------------------------
>
> Key: CASSANDRA-7622
> URL: https://issues.apache.org/jira/browse/CASSANDRA-7622
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Reporter: Tupshin Harper
> Fix For: 3.0
>
>
> 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.2#6252)
