[
https://issues.apache.org/jira/browse/CASSANDRA-7622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16396185#comment-16396185
]
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_r173966104
--- Diff: src/java/org/apache/cassandra/schema/TableMetadata.java ---
@@ -141,6 +147,15 @@ private TableMetadata(Builder builder)
params = builder.params.build();
isView = builder.isView;
+ isVirtual = builder.isVirtual;
+ if (isVirtual)
+ virtualKlass = builder.virtualKlass;
+ else
+ virtualKlass = null;
+
+ assert isVirtual == flags.contains(Flag.VIRTUAL) ||
!Strings.isNullOrEmpty(virtualKlass) && !flags.contains(Flag.VIRTUAL)
--- End diff --
Same as above w. the asserts. Let's just draw a line in the sand and stop
doing this.
> 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
