cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Lohfink (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-7622) Implement virtual tables
Date Tue, 13 Mar 2018 07:06:00 GMT


Chris Lohfink commented on CASSANDRA-7622:

Made some updates for NPs

> _can_ i drop a VT?
 yes, can drop and create with own classes on classpath. Cannot drop system_info though (same
protections as other system created local keyspaces exist)

> null class a legal state?

yes - if not a virtual table

> builder for statics

That was kinda awkward - trying to make more builder based in static block to define the virtual
tables schema like:
        Map<String, CQL3Type> definitions = new HashMap<>();
        definitions.put(KEYSPACE_NAME, CQL3Type.Native.TEXT);
        definitions.put(TABLE_NAME, CQL3Type.Native.TEXT);
        definitions.put(METRIC, CQL3Type.Native.TEXT);
        definitions.put(VALUE, CQL3Type.Native.TEXT);


> Implement virtual tables
> ------------------------
>                 Key: CASSANDRA-7622
>                 URL:
>             Project: Cassandra
>          Issue Type: Improvement
>            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