Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Sun, 2 Dec 2012 19:27:58 +0000 (UTC)
From: "Dave Brosius (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <1400225452.51121.1354476478381.JavaMail.jiratomcat@arcas>
In-Reply-To: <1824239272.51011.1354472038117.JavaMail.jiratomcat@arcas>
Subject: [jira] [Commented] (CASSANDRA-5012) alter table alter causes
 TSocket read 0 bytes
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/CASSANDRA-5012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13508332#comment-13508332 ] 

Dave Brosius commented on CASSANDRA-5012:
-----------------------------------------

Some exception occurred on the server, that caused the TSocket error. Finding and posting that error in the server logs, will help what went wrong.
                
> alter table alter causes TSocket read 0 bytes
> ---------------------------------------------
>
>                 Key: CASSANDRA-5012
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-5012
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 1.2.0 beta 2
>         Environment: On Mac OSX ./cqlsh
> Connected to Test Cluster at localhost:9160.
> [cqlsh 2.3.0 | Cassandra 1.2.0-rc1-SNAPSHOT | CQL spec 3.0.0 | Thrift protocol 19.35.0]
>            Reporter: Kristine Hahn
>
> Altering the type of a clustering key column causes TSocket error. 
> To reproduce the problem:
> 1. CREATE SCHEMA "Excalibur" WITH REPLICATION = { 'class' : 'SimpleStrategy', 'replication_factor' : 3 };
> 2. CREATE TABLE "Excalibur".Test ( id int, species text, color text, PRIMARY KEY ((id, species), color)) WITH compaction = { 'class' : 'SizeTieredCompactionStrategy', 'min_compaction_threshold' : 6 };
> 3. Alter table "Excalibur".test ALTER color type int;
> Expected result: Error message saying something like, "Changing the type of a clustering key is not allowed."
> Actual result: TSocket read 0 bytes

--
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