Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 68083200B25 for ; Wed, 8 Jun 2016 18:39:23 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 66FA3160A54; Wed, 8 Jun 2016 16:39:23 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id B09B0160A0E for ; Wed, 8 Jun 2016 18:39:22 +0200 (CEST) Received: (qmail 38966 invoked by uid 500); 8 Jun 2016 16:39:21 -0000 Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cassandra.apache.org Delivered-To: mailing list commits@cassandra.apache.org Received: (qmail 38873 invoked by uid 99); 8 Jun 2016 16:39:21 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 08 Jun 2016 16:39:21 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id B39E72C1F54 for ; Wed, 8 Jun 2016 16:39:21 +0000 (UTC) Date: Wed, 8 Jun 2016 16:39:21 +0000 (UTC) From: "Robert Stupp (JIRA)" To: commits@cassandra.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (CASSANDRA-7622) Implement virtual tables MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Wed, 08 Jun 2016 16:39:23 -0000 [ https://issues.apache.org/jira/browse/CASSANDRA-7622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15320891#comment-15320891 ] Robert Stupp commented on CASSANDRA-7622: ----------------------------------------- I'm with you, that sth like SHOW VARIABLES would be used from cqlsh. But the node just added as the initial contact point. When that node fails, the statement would be silently executed against another node. For SHOW VARIABLES this is not super dramatic - but for an ALTER SYSTEM DECOMMISSION it is. That's why I proposed {{WHERE node='1.2.3.4'}} as part of the syntax. At least, the coordinator can check, whether it finds its own IP in the WHERE clause. > Implement virtual tables > ------------------------ > > Key: CASSANDRA-7622 > URL: https://issues.apache.org/jira/browse/CASSANDRA-7622 > Project: Cassandra > Issue Type: Improvement > Reporter: Tupshin Harper > Assignee: Jeff Jirsa > Fix For: 3.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 (v6.3.4#6332)