[ https://issues.apache.org/jira/browse/CASSANDRA-7622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16395892#comment-16395892 ]
Chris Lohfink commented on CASSANDRA-7622: ------------------------------------------ PR has an abstract class thats more or less {code}public ReadQuery getQuery(SelectStatement selectStatement, QueryOptions options, DataLimits limits, int nowInSec) public void mutate(DecoratedKey partitionKey, Row row){code} This ultimately allows either supporting local or distributed since you can make a ReadQuery for coordination that collects from replicas (never done here though, but its possible). The {{system_info}} keyspace added for system metrics locally. To make it easier for simpler local tables created an InMemoryVirtualTable implementation that these all extend. Examples seen in [https://github.com/clohfink/cassandra/tree/7622-trunk/src/java/org/apache/cassandra/db/virtual] > Implement virtual tables > ------------------------ > > Key: CASSANDRA-7622 > URL: https://issues.apache.org/jira/browse/CASSANDRA-7622 > Project: Cassandra > Issue Type: Improvement > 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 > CASSANDRA-7370. > A possible implementation would be in terms of CASSANDRA-7443, but I am not > presupposing. -- This message was sent by Atlassian JIRA (v7.6.3#76005) --------------------------------------------------------------------- To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org