[
https://issues.apache.org/jira/browse/CASSANDRA-7622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16462426#comment-16462426
]
Aleksey Yeschenko commented on CASSANDRA-7622:
----------------------------------------------
Pushed the first review commit
[here|https://github.com/iamaleksey/cassandra/commits/7622-4.0].
It's the first commit in the series with the goal of separating virtual
keyspaces from real keyspaces on metadata level, with more to follow. This one
adds a new virtual keyspace - {{system_virtual_schema}} - with virtual tables
{{keyspaces}}, {{tables}}, and {{columns}} that mimic those of
{{system_schema}} to the extent that is reasonable to duplicate, and omits any
metadata that doesn't make any sense in context of virtual keyspaces
(properties like {{durable}} or {{replication}} for keyspaces, and most of the
param fields for tables). Among other things, this way evolution of arbitrary
virtual keyspaces becomes trivial, as you no longer have to worry with
incompatible previous schema stored persistently - because none of it is.
> 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
>
> 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]
