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 6A728DF9B for ; Wed, 19 Sep 2012 14:58:08 +0000 (UTC) Received: (qmail 76825 invoked by uid 500); 19 Sep 2012 14:58:07 -0000 Delivered-To: apmail-cassandra-commits-archive@cassandra.apache.org Received: (qmail 76782 invoked by uid 500); 19 Sep 2012 14:58:07 -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 76716 invoked by uid 99); 19 Sep 2012 14:58:07 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 19 Sep 2012 14:58:07 +0000 Date: Thu, 20 Sep 2012 01:58:07 +1100 (NCT) From: "Tyler Patterson (JIRA)" To: commits@cassandra.apache.org Message-ID: <276098892.97565.1348066687886.JavaMail.jiratomcat@arcas> Subject: [jira] [Created] (CASSANDRA-4689) Log error when using IN together with ORDER BY MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Tyler Patterson created CASSANDRA-4689: ------------------------------------------ Summary: Log error when using IN together with ORDER BY Key: CASSANDRA-4689 URL: https://issues.apache.org/jira/browse/CASSANDRA-4689 Project: Cassandra Issue Type: Bug Environment: built from source on cassandra-1.1 (b43cc362aa568a46bc53e545c68518b0bd350b76) os: ubuntu Reporter: Tyler Patterson Assignee: Pavel Yaskevich {code} $ bin/cqlsh -3 Connected to Test Cluster at localhost:9160. [cqlsh 2.2.0 | Cassandra 1.1.5-SNAPSHOT | CQL spec 3.0.0 | Thrift protocol 19.32.0] Use HELP for help. cqlsh> use ks; cqlsh:ks> drop TABLE test; cqlsh:ks> CREATE TABLE test (my_id varchar, time_id uuid, value int, PRIMARY KEY (my_id, time_id)); cqlsh:ks> INSERT INTO test (my_id, time_id, value) VALUES ('key1', 1, 1); cqlsh:ks> INSERT INTO test (my_id, time_id, value) VALUES ('key2', 2, 2); cqlsh:ks> select * from test where my_id in('key1', 'key2') order by time_id; TSocket read 0 bytes {code} The log shows this: {code} ERROR [Thrift:5] 2012-09-19 08:44:59,859 CustomTThreadPoolServer.java (line 204) Error occurred during processing of message. java.lang.IllegalArgumentException: Column time_id wasn't found in select clause. at org.apache.cassandra.cql3.statements.SelectStatement.getColumnPositionInSelect(SelectStatement.java:866) at org.apache.cassandra.cql3.statements.SelectStatement.orderResults(SelectStatement.java:836) at org.apache.cassandra.cql3.statements.SelectStatement.process(SelectStatement.java:807) at org.apache.cassandra.cql3.statements.SelectStatement.execute(SelectStatement.java:137) at org.apache.cassandra.cql3.QueryProcessor.processStatement(QueryProcessor.java:108) at org.apache.cassandra.cql3.QueryProcessor.process(QueryProcessor.java:121) at org.apache.cassandra.thrift.CassandraServer.execute_cql_query(CassandraServer.java:1242) at org.apache.cassandra.thrift.Cassandra$Processor$execute_cql_query.getResult(Cassandra.java:3542) at org.apache.cassandra.thrift.Cassandra$Processor$execute_cql_query.getResult(Cassandra.java:3530) 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:186) 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:662) {code} NOTE: This issue appears similar to https://issues.apache.org/jira/browse/CASSANDRA-4612 from the user perspective, even though 4612 was verified as fixed. -- 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