Chris Lohfink commented on CASSANDRA-7622:

Well with my proposed implementation there is only a single system 
non-replicated keyspace containing virtual tables and you cant create them so 
thats not really an issue. When we add support to allow people create virtual 
tables that could easily be limited to local replicated or a keyspace flagged 
with virtual.

With this implementation worth noting that theres nothing preventing an 
implementor from using the keyspace's replication factor and distributing 
accordingly, but the in memory virtual table used in the system keyspace are 
all setup for local replication, so the limitation (on a local RF) on create 
could be placed on that implementation of VirtualTable.

> 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 
> A possible implementation would be in terms of CASSANDRA-7443, but I am not 
> presupposing.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

Reply via email to