[ 
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_r173965848
  
    --- Diff: src/java/org/apache/cassandra/schema/Schema.java ---
    @@ -713,20 +727,24 @@ private void dropView(ViewMetadata metadata)
     
         private void dropTable(TableMetadata metadata)
         {
    -        ColumnFamilyStore cfs = 
Keyspace.open(metadata.keyspace).getColumnFamilyStore(metadata.name);
    -        assert cfs != null;
    -        // make sure all the indexes are dropped, or else.
    -        cfs.indexManager.markAllIndexesRemoved();
    -        
CompactionManager.instance.interruptCompactionFor(Collections.singleton(metadata),
 true);
    -        if (DatabaseDescriptor.isAutoSnapshot())
    -            
cfs.snapshot(Keyspace.getTimestampedSnapshotNameWithPrefix(cfs.name, 
ColumnFamilyStore.SNAPSHOT_DROP_PREFIX));
    -        
CommitLog.instance.forceRecycleAllSegments(Collections.singleton(metadata.id));
    --- End diff --
    
    I'll go back and look through comments, but _can_ i drop a VT? 
)

> 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