[
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_r173958314
--- Diff:
src/java/org/apache/cassandra/cql3/statements/ModificationStatement.java ---
@@ -267,12 +267,18 @@ public boolean updatesRegularRows()
// columns is if we set some static columns, and in that case no
clustering
// columns should be given. So in practice, it's enough to check
if we have
// either the table has no clustering or if it has at least one of
them set.
- return metadata().clusteringColumns().isEmpty() ||
restrictions.hasClusteringColumnsRestrictions();
+ return !metadata().isVirtual() &&
--- End diff --
nit: why use the method if we have it locally (and it's public anyhoo). The
object reference is being used elsewhere herein already.
)
> 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: [email protected]
For additional commands, e-mail: [email protected]
