[
https://issues.apache.org/jira/browse/CASSANDRA-7622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16480823#comment-16480823
]
Aleksey Yeschenko commented on CASSANDRA-7622:
----------------------------------------------
CI passed ([here|https://circleci.com/gh/iamaleksey/cassandra/295] and
[here|https://circleci.com/gh/iamaleksey/cassandra/296]). Committed as
[0d464cd25ffbb5734f96c3082f9cc35011de366|https://github.com/apache/cassandra/commit/0d464cd25ffbb5734f96c3082f9cc35011de3667]
with nits addressed.
Thanks [~cnlwsu] and [~blerer] for you work and patience.
> 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.0
>
> Attachments: screenshot-1.png
>
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
