[ 
https://issues.apache.org/jira/browse/CASSANDRA-7622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nate McCall updated CASSANDRA-7622:
-----------------------------------
    Comment: was deleted

(was: Github user zznate commented on a diff in the pull request:

    https://github.com/apache/cassandra/pull/205#discussion_r173964951
  
    --- Diff: src/java/org/apache/cassandra/db/virtual/SystemInfoKeyspace.java 
---
    @@ -0,0 +1,63 @@
    +package org.apache.cassandra.db.virtual;
    +
    +import static java.lang.String.format;
    +
    +import java.util.List;
    +
    +import org.apache.cassandra.cql3.statements.CreateTableStatement;
    +import org.apache.cassandra.schema.KeyspaceMetadata;
    +import org.apache.cassandra.schema.KeyspaceParams;
    +import org.apache.cassandra.schema.SchemaConstants;
    +import org.apache.cassandra.schema.TableId;
    +import org.apache.cassandra.schema.TableMetadata;
    +import org.apache.cassandra.schema.Tables;
    +import org.slf4j.Logger;
    +import org.slf4j.LoggerFactory;
    +
    +import com.google.common.collect.ImmutableList;
    +
    +public class SystemInfoKeyspace
    +{
    +    private static final Logger logger = 
LoggerFactory.getLogger(SystemInfoKeyspace.class);
    +
    +    private SystemInfoKeyspace() {}
    +
    +    public static final String SETTINGS = "settings";
    --- End diff --
    
    yay! statics!
)

> Implement virtual tables
> ------------------------
>
>                 Key: CASSANDRA-7622
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-7622
>             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
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

Reply via email to