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 3918E1726C for ; Wed, 5 Nov 2014 22:48:34 +0000 (UTC) Received: (qmail 38560 invoked by uid 500); 5 Nov 2014 22:48:34 -0000 Delivered-To: apmail-cassandra-commits-archive@cassandra.apache.org Received: (qmail 38521 invoked by uid 500); 5 Nov 2014 22:48: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 38503 invoked by uid 99); 5 Nov 2014 22:48:34 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 05 Nov 2014 22:48:34 +0000 Date: Wed, 5 Nov 2014 22:48:33 +0000 (UTC) From: "Philip Thompson (JIRA)" To: commits@cassandra.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (CASSANDRA-8262) parse_for_table_meta errors out on queries with undefined grammars 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-8262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14199277#comment-14199277 ] Philip Thompson commented on CASSANDRA-8262: -------------------------------------------- /cc [~mishail] [~thobbs] In 2.1.0, if a cqlsh query returned 0 rows, all that is printed is {{(0 rows)}}. After CASSANDRA-6910, it also prints out the table metadata. If table metadata cannot be determined, is it acceptable to just fall back to the 2.1.0 output, or would you also like a warning message that says table metadata could not be determined? > parse_for_table_meta errors out on queries with undefined grammars > ------------------------------------------------------------------ > > Key: CASSANDRA-8262 > URL: https://issues.apache.org/jira/browse/CASSANDRA-8262 > Project: Cassandra > Issue Type: Bug > Reporter: Philip Thompson > Assignee: Philip Thompson > Labels: cqlsh > Fix For: 2.1.2 > > Attachments: cassandra-2.1-8262-1.txt > > > CASSANDRA-6910 introduced changes to the cqlsh function {{parse_for_table_meta}} that cause an error to be thrown whenever a query does not have its grammar defined in cql3handling.py. However, this is affecting queries that are legitimate cql syntax and are accepted by Cassandra, but aren't defined in cqlsh. -- This message was sent by Atlassian JIRA (v6.3.4#6332)