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 33B50D1BA for ; Thu, 16 Aug 2012 22:03:45 +0000 (UTC) Received: (qmail 10865 invoked by uid 500); 16 Aug 2012 22:03:44 -0000 Delivered-To: apmail-cassandra-commits-archive@cassandra.apache.org Received: (qmail 10832 invoked by uid 500); 16 Aug 2012 22:03:44 -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 10766 invoked by uid 99); 16 Aug 2012 22:03:44 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 16 Aug 2012 22:03:44 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 1CF212C5AC9 for ; Thu, 16 Aug 2012 22:03:43 +0000 (UTC) Date: Fri, 17 Aug 2012 09:03:43 +1100 (NCT) From: "Kirk True (JIRA)" To: commits@cassandra.apache.org Message-ID: <1273238777.21255.1345154624119.JavaMail.jiratomcat@arcas> In-Reply-To: <900003083.21250.1345154377960.JavaMail.jiratomcat@arcas> Subject: [jira] [Updated] (CASSANDRA-4552) cqlsh doesn't handle Int32Type when fully-qualified package name is present 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-4552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk True updated CASSANDRA-4552: --------------------------------- Attachment: trunk-4552.txt The value of the cqlsh Python script's {{casstype}} is in some cases the fully-qualified package name. In my case it was {{org.apache.cassandra.db.marshal.Int32Type}} while it appears the code is expecting it to be simply {{Int32Type}}. I don't think this is the right fix, but it's a start and it unblocks me :) > cqlsh doesn't handle Int32Type when fully-qualified package name is present > --------------------------------------------------------------------------- > > Key: CASSANDRA-4552 > URL: https://issues.apache.org/jira/browse/CASSANDRA-4552 > Project: Cassandra > Issue Type: Bug > Components: Tools > Affects Versions: 1.2.0 > Environment: Today's (08/16/2012) trunk. > Reporter: Kirk True > Assignee: Kirk True > Fix For: 1.2.0 > > Attachments: trunk-4552.txt > > > Steps to reproduce: > 1. Start Cassandra > 2. Start cqlsh: {{./bin/cqlsh -3 --debug}} > 3. Execute these statements: > {noformat} > create keyspace foo with strategy_class = 'SimpleStrategy' and strategy_options:replication_factor=1; > use foo; > create table bar ( > a int, > b int, > primary key (a) > ); > insert into bar (a, b) values (1, 1); > select * from bar; > {noformat} > Expected: to see my row results > Actual: I see this error: > {noformat} > Traceback (most recent call last): > File "./bin/cqlsh", line 926, in onecmd > self.handle_statement(st, statementtext) > File "./bin/cqlsh", line 954, in handle_statement > return custom_handler(parsed) > File "./bin/cqlsh", line 1015, in do_select > self.perform_statement(parsed.extract_orig(), decoder=decoder) > File "./bin/cqlsh", line 1042, in perform_statement > self.print_result(self.cursor) > File "./bin/cqlsh", line 1096, in print_result > self.print_static_result(cursor) > File "./bin/cqlsh", line 1112, in print_static_result > formatted_data = [map(self.myformat_value, row, coltypes) for row in cursor] > File "./bin/cqlsh", line 622, in myformat_value > float_precision=self.display_float_precision, **kwargs) > File "./bin/cqlsh", line 504, in format_value > escapedval = val.replace('\\', '\\\\') > AttributeError: 'int' object has no attribute 'replace' > {noformat} > This is similar to CASSANDRA-4083 in terms of the error message, but may be of a different cause. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira