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 68C9AE9C1 for ; Mon, 25 Feb 2013 13:58:26 +0000 (UTC) Received: (qmail 44637 invoked by uid 500); 25 Feb 2013 13:58:26 -0000 Delivered-To: apmail-cassandra-commits-archive@cassandra.apache.org Received: (qmail 44581 invoked by uid 500); 25 Feb 2013 13:58:26 -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 44566 invoked by uid 99); 25 Feb 2013 13:58:25 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 25 Feb 2013 13:58:25 +0000 Date: Mon, 25 Feb 2013 13:58:25 +0000 (UTC) From: "Sylvain Lebresne (JIRA)" To: commits@cassandra.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (CASSANDRA-5138) Provide a better CQL error when table data does not conform to CQL metadata. 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-5138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylvain Lebresne updated CASSANDRA-5138: ---------------------------------------- Fix Version/s: (was: 1.2.2) 1.2.3 > Provide a better CQL error when table data does not conform to CQL metadata. > ---------------------------------------------------------------------------- > > Key: CASSANDRA-5138 > URL: https://issues.apache.org/jira/browse/CASSANDRA-5138 > Project: Cassandra > Issue Type: Bug > Components: Core > Affects Versions: 1.2.0 > Environment: Mac OS X running 1.2 > Reporter: Brian ONeill > Assignee: Sylvain Lebresne > Priority: Minor > Fix For: 1.2.3 > > Attachments: northpole.cql > > > When you create a table via CQL, then insert into it via Thrift. If you inadvertently leave out a component of the column name, in CQL you receive a: > TSocket read 0 bytes > Server-side the following exception is logged: > ERROR 15:19:18,016 Error occurred during processing of message. > java.lang.ArrayIndexOutOfBoundsException: 3 > at org.apache.cassandra.cql3.statements.ColumnGroupMap.add(ColumnGroupMap.java:43) > at org.apache.cassandra.cql3.statements.ColumnGroupMap.access$200(ColumnGroupMap.java:31) > at org.apache.cassandra.cql3.statements.ColumnGroupMap$Builder.add(ColumnGroupMap.java:138) > at org.apache.cassandra.cql3.statements.SelectStatement.process(SelectStatement.java:805) > at org.apache.cassandra.cql3.statements.SelectStatement.processResults(SelectStatement.java:145) > at org.apache.cassandra.cql3.statements.SelectStatement.execute(SelectStatement.java:134) > at org.apache.cassandra.cql3.statements.SelectStatement.execute(SelectStatement.java:61) > at org.apache.cassandra.cql3.QueryProcessor.processStatement(QueryProcessor.java:132) > at org.apache.cassandra.cql3.QueryProcessor.process(QueryProcessor.java:140) > at org.apache.cassandra.thrift.CassandraServer.execute_cql3_query(CassandraServer.java:1686) > at org.apache.cassandra.thrift.Cassandra$Processor$execute_cql3_query.getResult(Cassandra.java:4074) > at org.apache.cassandra.thrift.Cassandra$Processor$execute_cql3_query.getResult(Cassandra.java:4062) > at org.apache.thrift.ProcessFunction.process(ProcessFunction.java:32) > at org.apache.thrift.TBaseProcessor.process(TBaseProcessor.java:34) > at org.apache.cassandra.thrift.CustomTThreadPoolServer$WorkerProcess.run(CustomTThreadPoolServer.java:199) > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) > at java.lang.Thread.run(Thread.java:680) > I'll submit a schema, and steps to reproduce. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira