Return-Path: X-Original-To: apmail-cassandra-commits-archive@www.apache.org Delivered-To: apmail-cassandra-commits-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id F0FFC17B62 for ; Tue, 30 Sep 2014 22:14:35 +0000 (UTC) Received: (qmail 92823 invoked by uid 500); 30 Sep 2014 22:14:34 -0000 Delivered-To: apmail-cassandra-commits-archive@cassandra.apache.org Received: (qmail 92790 invoked by uid 500); 30 Sep 2014 22:14:34 -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 92779 invoked by uid 99); 30 Sep 2014 22:14:34 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 30 Sep 2014 22:14:34 +0000 Date: Tue, 30 Sep 2014 22:14:34 +0000 (UTC) From: "Robert Stupp (JIRA)" To: commits@cassandra.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (CASSANDRA-8005) Server-side DESCRIBE MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CASSANDRA-8005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14153871#comment-14153871 ] Robert Stupp commented on CASSANDRA-8005: ----------------------------------------- Especially backup tools should exactly know what they're doing - these need to inspect the schema tables anyway. Dump & load might be a valid use-case for server-side DESC support - could work fine with that JSON style select and update (CASSANDRA-7970). But then there would be demand to provide an "UPSERT style CREATE TABLE" (just to apply the changes like added columns). > Server-side DESCRIBE > -------------------- > > Key: CASSANDRA-8005 > URL: https://issues.apache.org/jira/browse/CASSANDRA-8005 > Project: Cassandra > Issue Type: New Feature > Components: API > Reporter: Tyler Hobbs > Priority: Minor > Labels: cql3 > Fix For: 3.0 > > > The various {{DESCRIBE}} commands are currently implemented by cqlsh, and nearly identical implementations exist in many drivers. There are several motivations for making {{DESCRIBE}} part of the CQL language: > * Eliminate the (fairly complex) duplicate implementations across drivers and cqlsh > * Get closer to allowing drivers to not have to fetch the schema tables. (Minor changes to prepared statements are also needed.) > * Have instantaneous support for new schema features in cqlsh. (You currently have to update the bundled python driver.) > * Support writing out schemas where it makes sense. One good example of this is backups. You need to restore the schema before restoring data in the case of total loss, so it makes sense to write out the schema alongside snapshots. -- This message was sent by Atlassian JIRA (v6.3.4#6332)