[ https://issues.apache.org/jira/browse/CASSANDRA-7622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16395886#comment-16395886 ]
ASF GitHub Bot commented on CASSANDRA-7622: ------------------------------------------- GitHub user clohfink opened a pull request: https://github.com/apache/cassandra/pull/205 Add virtual tables for CASSANDRA-7622 You can merge this pull request into a Git repository by running: $ git pull https://github.com/clohfink/cassandra 7622-trunk Alternatively you can review and apply these changes as the patch at: https://github.com/apache/cassandra/pull/205.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #205 ---- commit 170e71e2b0b6e26e7092f9a35b0f166676d073f6 Author: Chris Lohfink <clohfink@...> Date: 2018-03-12T20:53:39Z Add virtual tables for CASSANDRA-7622 ---- > 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