cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jeff Jirsa (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-7622) Implement virtual tables
Date Mon, 06 Jun 2016 16:25:21 GMT


Jeff Jirsa commented on CASSANDRA-7622:

Thanks [~blerer] - {{CREATE VIRTUAL TABLE}} with {{class}} in {{virtual_table_options}} seems
consistent with compaction and easy to understand. I do believe it's possible for the virtual
table to accomplish this with {{QueryState state, QueryOptions options}} arguments, but it
would have a lot of non-trivial, duplicate code in each virtual table, and I agree there's
a better way. Will refine the proposal.

> 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