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 Fri, 27 Apr 2018 05:00:01 GMT


Chris Lohfink commented on CASSANDRA-7622:

While waiting for other implementation, made some changes on some feedback out of band:
 * Use same QueryPager as other ReadCommands
 * Remove virtual tables from the system_schema.tables. Moved into \{{system_schemas.virtual_tables}}.
The drivers will need to add the TableMetadata from that in order to have it in own metadata,
for cqlsh I added a temp override until it exists in driver to make easier to play with.
 * Added the missed support for IN on partitions (so can do relations or IN clause for partition
key, or both on parts of key). I think this can be done better but seems to function on things
Ive thought of.
 * Some minor cleaning/renaming


> 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
>         Attachments: screenshot-1.png
> 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