[
https://issues.apache.org/jira/browse/CASSANDRA-7622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14540103#comment-14540103
]
Benjamin Lerer commented on CASSANDRA-7622:
-------------------------------------------
As discussed with [~iamaleksey] off line, what we want to allow for virtual
table is the following:
* limited {{SELECT}}: select all or select where with complete primary key
* limited {{UPDATE}}: no {{DELETE}}, no {{INSERT}} only {{UPDATE SET}} (It is
required for some setter that are exposed via JMX)
* the data returned or updated will only be the data of the host
* virtual tables will not be accessible via Thrift
The plan is to reuse the parsing logic and a bit of {{SelectStatement}} and
{{UpdateStatement}}.
> 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
> Assignee: Benjamin Lerer
> 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)
