[
https://issues.apache.org/jira/browse/CASSANDRA-7622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16425076#comment-16425076
]
Dinesh Joshi commented on CASSANDRA-7622:
-----------------------------------------
[~cnlwsu], I spent some time looking at the patch. My initial thoughts on the
implementation are that we should probably have a separate {{VirtualKeyspace}}
like we have a {{SystemKeyspace}}. This will allow us to isolate / namespace
{{VirtualTables}}. We can always change this if needed. One of the advantage, I
think, is that this keyspace can become available for serving sooner (we would
ofcourse need to change the bootstrap for this to work). If we're exposing
metrics or other internal state then this would be very helpful. What do you
think?
> 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
> 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
