You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Kristine Hahn (JIRA)" <ji...@apache.org> on 2012/12/02 19:13:57 UTC

[jira] [Created] (CASSANDRA-5012) alter table alter causes TSocket read 0 bytes

Kristine Hahn created CASSANDRA-5012:
----------------------------------------

             Summary: 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 cause 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

[jira] [Commented] (CASSANDRA-5012) alter table alter causes TSocket read 0 bytes

Posted by "Dave Brosius (JIRA)" <ji...@apache.org>.
    [ 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

[jira] [Updated] (CASSANDRA-5012) alter table alter causes TSocket read 0 bytes

Posted by "Kristine Hahn (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/CASSANDRA-5012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kristine Hahn updated CASSANDRA-5012:
-------------------------------------

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

  was:
Altering the type of a clustering key column cause 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

    
> 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

[jira] [Updated] (CASSANDRA-5012) alter table alter causes TSocket read 0 bytes

Posted by "Kristine Hahn (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/CASSANDRA-5012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kristine Hahn updated CASSANDRA-5012:
-------------------------------------

    Attachment: log.txt

Sorry for not including the log. Here it is if you're still interested in it.
                
> 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
>            Assignee: Sylvain Lebresne
>             Fix For: 1.2.0
>
>         Attachments: 5012.patch, log.txt
>
>
> 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

[jira] [Updated] (CASSANDRA-5012) alter table alter causes TSocket read 0 bytes

Posted by "Sylvain Lebresne (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/CASSANDRA-5012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sylvain Lebresne updated CASSANDRA-5012:
----------------------------------------

    Attachment: 5012.patch

Patch attached to move the validation at the time of the application of the alter statement.
                
> 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
>             Fix For: 1.2.0
>
>         Attachments: 5012.patch
>
>
> 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