cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-7622) Implement virtual tables
Date Mon, 12 Mar 2018 22:27:04 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-7622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16396172#comment-16396172
] 

ASF GitHub Bot commented on CASSANDRA-7622:
-------------------------------------------

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

    https://github.com/apache/cassandra/pull/205#discussion_r173962324
  
    --- Diff: src/java/org/apache/cassandra/db/Keyspace.java ---
    @@ -331,8 +337,11 @@ private Keyspace(String keyspaceName, boolean loadSSTables)
             this.viewManager = new ViewManager(this);
             for (TableMetadata cfm : metadata.tablesAndViews())
             {
    -            logger.trace("Initializing {}.{}", getName(), cfm.name);
    -            initCf(Schema.instance.getTableMetadataRef(cfm.id), loadSSTables);
    +            logger.info("Initializing {}.{}", getName(), cfm.name);
    --- End diff --
    
    Change from trace() to info() intentional?


> 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-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org


Mime
View raw message