Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Fri, 25 Jul 2014 16:28:38 +0000 (UTC)
From: "Tupshin Harper (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12729761.1406305663566.45486.1406305718377@arcas>
In-Reply-To: <JIRA.12729761.1406305663566@arcas>
References: <JIRA.12729761.1406305663566@arcas>
Subject: [jira] [Created] (CASSANDRA-7622) Implement virtual tables
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Tupshin Harper created CASSANDRA-7622:
-----------------------------------------

             Summary: Implement virtual tables
                 Key: CASSANDRA-7622
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-7622
             Project: Cassandra
          Issue Type: Improvement
          Components: Core
            Reporter: Tupshin Harper
             Fix For: 3.0


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.2#6252)