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 0762A200B27 for ; Tue, 7 Jun 2016 23:43:23 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 06006160A36; Tue, 7 Jun 2016 21:43: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 4AA9C160968 for ; Tue, 7 Jun 2016 23:43:22 +0200 (CEST) Received: (qmail 47596 invoked by uid 500); 7 Jun 2016 21:43: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 47554 invoked by uid 99); 7 Jun 2016 21:43:21 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 07 Jun 2016 21:43:21 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 43FED2C1F75 for ; Tue, 7 Jun 2016 21:43:21 +0000 (UTC) Date: Tue, 7 Jun 2016 21:43:21 +0000 (UTC) From: "Jon Haddad (JIRA)" To: commits@cassandra.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Comment Edited] (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: Tue, 07 Jun 2016 21:43:23 -0000 [ https://issues.apache.org/jira/browse/CASSANDRA-7622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15319499#comment-15319499 ] Jon Haddad edited comment on CASSANDRA-7622 at 6/7/16 9:42 PM: --------------------------------------------------------------- I agree with [~tupshin] that we'll want to be able to write to those tables as well, but I'd rather see a first cut in a tick tock release of read only tables, then a follow up 2 months later with writes, rather than having to wait for the whole thing. Getting access to metrics in a read only, non JMX fashion would be awesome from an operational perspective and be 100% worth it by itself. I also +1 that it's totally fine to avoid thinking about replication. was (Author: rustyrazorblade): I agree with [~tupshin] that we'll want to be able to write to those tables as well, but I'd rather see a first cut in a tick tock release of read only tables, then a follow up 2 months later with writes, rather than having to wait for the whole thing. Getting access to metrics in a read only, non JMX fashion would be awesome from an operational perspective and be 100% worth it by itself. > 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)