[ https://issues.apache.org/jira/browse/CASSANDRA-7622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15320961#comment-15320961 ]
Sylvain Lebresne commented on CASSANDRA-7622: --------------------------------------------- bq. Sure, but SHOW is a common enough command in DB world Imo, the general mechanism of virtual tables should be just an implementation detail for exposing a table. That means even in the case of {{SHOW VARIABLES}}, we'd really be adding a new system table with those variables, and we'll be able to query it through normal select. That certainly doesn't prevent us for supporting {{SHOW VARIABLES}} as syntactic sugar for the equivalent select statement. This might even make sense as a cqlsh thing (rather than a CQL one). > 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)