[ https://issues.apache.org/jira/browse/CASSANDRA-7622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15320874#comment-15320874 ]
Brian Hess commented on CASSANDRA-7622: ---------------------------------------- If the plan is to enable writing to these virtual tables, then we should think more about a SELECT type syntax. That would make the future UPDATE operations make a lot more sense. And if we are thinking that eventually we will enable user-defined VTs then INSERT and DELETE operations may make sense. There really is no need for special syntax here, so I'd caution against that. For that reason, I'd suggest we stick with SELECT syntax even in this first use case - in a forward thinking way. > 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)