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 5572E17FFC for ; Wed, 1 Oct 2014 16:08:35 +0000 (UTC) Received: (qmail 673 invoked by uid 500); 1 Oct 2014 16:08:35 -0000 Delivered-To: apmail-cassandra-commits-archive@cassandra.apache.org Received: (qmail 645 invoked by uid 500); 1 Oct 2014 16:08:35 -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 633 invoked by uid 99); 1 Oct 2014 16:08:35 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 Oct 2014 16:08:35 +0000 Date: Wed, 1 Oct 2014 16:08:35 +0000 (UTC) From: "Russ Hatch (JIRA)" To: commits@cassandra.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (CASSANDRA-8030) cqlsh error when selecting data from a table with nested UDTs 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-8030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14154990#comment-14154990 ] Russ Hatch commented on CASSANDRA-8030: --------------------------------------- I think it probably falls under the domain of the python driver to be able to work without blist installed in this scenario, I went ahead and created a ticket here for the issue: https://datastax-oss.atlassian.net/browse/PYTHON-167 > cqlsh error when selecting data from a table with nested UDTs > ------------------------------------------------------------- > > Key: CASSANDRA-8030 > URL: https://issues.apache.org/jira/browse/CASSANDRA-8030 > Project: Cassandra > Issue Type: Bug > Environment: Ubuntu 14.04. Cassandra 2.1.0. Single node. > Reporter: Cory Snyder > Labels: cqlsh > Attachments: example_statements.txt, schema.txt > > > The schema that was being used when this error was produced is attached. Whenever I try to select data from the LOAD_BALANCER_SERVICE table after having written data with non-empty sets for either the pools or virtual_servers fields, cqlsh fails with the following exception: > {code} > Traceback (most recent call last): > File "/usr/bin/cqlsh", line 909, in perform_simple_statement > rows = self.session.execute(statement, trace=self.tracing_enabled) > File "/usr/share/cassandra/lib/cassandra-driver-internal-only-2.1.0.post.zip/cassandra-driver-2.1.0.post/cassandra/cluster.py", line 1281, in execute > result = future.result(timeout) > File "/usr/share/cassandra/lib/cassandra-driver-internal-only-2.1.0.post.zip/cassandra-driver-2.1.0.post/cassandra/cluster.py", line 2772, in result > raise self._final_exception > TypeError: unhashable type: 'set' > {code} > I am, however, able to select the data from the table with the Java Datastax driver. I am also able to select data from the table if both the pools and virtual_servers fields are empty sets. -- This message was sent by Atlassian JIRA (v6.3.4#6332)