[
https://issues.apache.org/jira/browse/CASSANDRA-7622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16452700#comment-16452700
]
Jeff Jirsa edited comment on CASSANDRA-7622 at 4/25/18 5:31 PM:
----------------------------------------------------------------
{quote}
Around mid-February, I wanted to come back to that ticket. At that time it was
assigned to Jeff and I knew he was not actively working on it.
{quote}
I dunno why you'd think that, I gave a talk about it at NGCC in September where
I indicated it was something we were actively working on.
was (Author: jjirsa):
{quote}
Around mid-February, I wanted to come back to that ticket. At that time it was
assigned to Jeff and I knew he was not actively working on it.
{quote}
I dunno why you'd think that, I gave a talk about it at NGCC in October where I
indicated it was something we were actively working on.
> 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: [email protected]
For additional commands, e-mail: [email protected]
