Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Tue, 7 Jun 2016 21:53:21 +0000 (UTC)
From: "Jon Haddad (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12729761.1406305663000.20381.1465336401537@Atlassian.JIRA>
In-Reply-To: <JIRA.12729761.1406305663000@Atlassian.JIRA>
References: <JIRA.12729761.1406305663000@Atlassian.JIRA> <JIRA.12729761.1406305663566@arcas>
Subject: [jira] [Commented] (CASSANDRA-7622) Implement virtual tables
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Tue, 07 Jun 2016 21:53:23 -0000


    [ https://issues.apache.org/jira/browse/CASSANDRA-7622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15319514#comment-15319514 ] 

Jon Haddad commented on CASSANDRA-7622:
---------------------------------------

So... exactly what I said?  :)

> Implement virtual tables
> ------------------------
>
>                 Key: CASSANDRA-7622
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-7622
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Tupshin Harper
>            Assignee: Jeff Jirsa
>             Fix For: 3.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
(v6.3.4#6332)