[
https://issues.apache.org/jira/browse/CASSANDRA-7622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16397045#comment-16397045
]
Jeff Jirsa commented on CASSANDRA-7622:
---------------------------------------
At NGCC I tried to make an argument for their general availabiluty, guarded
behind some experimental flag that gave us the opportunity to change the API or
remove them later
I believe there are some general purpose use cases (for example, analogous to
foreign data wrappers) that I expect real users to appreciate, but I also
realize that it’s a young feature that is likely going to change/evolve
I agree we should guard it. I’d like to see it in arbitrary keyspaces, but I
don’t necessarily feel it needs to happen immediately , maybe in v5
> 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
