cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aleksey Yeschenko (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-7622) Implement virtual tables
Date Wed, 04 Apr 2018 15:53:00 GMT


Aleksey Yeschenko commented on CASSANDRA-7622:

The right level of abstraction, for both this and pluggable storage, is on keyspace level.
The basic write unit we have is a {{Mutation}}, and you have to accept this. What would not
be acceptable is if-else conditions in {{Keyspace.apply()}} depending on what the kind of
table this is.

Additionally, all tables in a keyspace by definition share the same replication strategy and
params, and I just don't see how you can mix and match regular and virtual ones in the same

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

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message