[
https://issues.apache.org/jira/browse/CASSANDRA-7622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16456572#comment-16456572
]
Aleksey Yeschenko commented on CASSANDRA-7622:
----------------------------------------------
bq. For instance, I do have a major high level concerns on the current patch in
that I am strongly in favor of not shipping syntax for creating virtual tables,
at least for the initial commit. I am completely sold on virtual tables as a
mean to expose configuration infos and metrics, but I'm a lot less sold about
letting user create their own.
No disagreement here. We don't want it to be exposed in regular DDL. However,
we would like this to be at least a little bit generic, so that one could
plug-in extra virtual keyspaces on C* startup, similar to how some folks/forks
add extra system keyspaces and system tables. There are some use cases for
virtual tables that we want to experiment with ([~jjirsa] gave a few examples
in his NGCC talk) that are compelling enough to at least allow this possibility.
> 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: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
