[CASSANDRA-7622] Implement virtual tables

• Type: Improvement
• Status: Resolved
• Priority: Normal
• Resolution: Fixed
• Fix Version/s: 4.0-alpha1, 4.0
• Component/s: Legacy/CQL
• Labels: virtual-tables
• Assignee: Chris Lohfink
• Reporter: Tupshin Harper

Authors

Chris Lohfink

Reviewers

Aleksey Yeschenko

• Created: 25/Jul/14 16:27
• Updated: 15/May/20 08:03
• Resolved: 18/May/18 15:48

Description

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.

Issue Links

• contains: CASSANDRA-3527 Expose JMX values via CQL interface
• Dependent: CASSANDRA-11994 Expose metrics via CQL interface
• is depended upon by: CASSANDRA-9233 Allow system variables to be retrieved and set via CQL
• is duplicated by: CASSANDRA-12115 Command that returns the seeds
• is related to: CASSANDRA-7443 Extend Descriptor to include a format value and refactor reader/writer apis
• relates to: CASSANDRA-14259 Nodetool command is not accessible with read-only account.
• relates to: CASSANDRA-7370 Create a new system table "node_config" to load cassandra.yaml config data.