cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jon Haddad (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-7622) Implement virtual tables
Date Tue, 07 Jun 2016 21:42:21 GMT


Jon Haddad commented on CASSANDRA-7622:

I agree with [~tupshin] that we'll want to be able to write to those tables as well, but I'd
rather see a first cut in a tick tock release of read only tables, then a follow up 2 months
later with writes, rather than having to wait for the whole thing.  Getting access to metrics
in a read only, non JMX fashion would be awesome from an operational perspective and be 100%
worth it by itself.

> Implement virtual tables
> ------------------------
>                 Key: CASSANDRA-7622
>                 URL:
>             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

View raw message