cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Carl Yeksigian (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-5882) Changing column type from int to bigint or vice versa causes decoding errors.
Date Wed, 21 Aug 2013 14:19:51 GMT

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

Carl Yeksigian commented on CASSANDRA-5882:
-------------------------------------------

a couple of misspelled comments: s/let is fly/let it fly/; s/changet/change/


                
> Changing column type from int to bigint or vice versa causes decoding errors.
> -----------------------------------------------------------------------------
>
>                 Key: CASSANDRA-5882
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-5882
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>            Reporter: J.B. Langston
>            Assignee: Sylvain Lebresne
>             Fix For: 1.2.9
>
>         Attachments: 5882.txt
>
>
> cqlsh:dbsite> create table testint (id uuid, bestof bigint, primary key (id) );
> cqlsh:dbsite> insert into testint (id, bestof ) values (49d30f84-a409-4433-ad60-eb9c1a06b7bb,
1376399966);
> cqlsh:dbsite> insert into testint (id, bestof ) values (6cab4798-ad29-4419-bd59-308f9ec3bc44,
1376389800);
> cqlsh:dbsite> insert into testint (id, bestof ) values (685bb9ff-a4fe-4e47-95eb-f6a353d9e179,
1376390400);
> cqlsh:dbsite> insert into testint (id, bestof ) values (a848f832-5ded-4ef7-bf4b-7db561564c57,
1376391000);
> cqlsh:dbsite> select * from testint ;
>  id                                   | bestof
> --------------------------------------+------------
>  a848f832-5ded-4ef7-bf4b-7db561564c57 | 1376391000
>  49d30f84-a409-4433-ad60-eb9c1a06b7bb | 1376399966
>  6cab4798-ad29-4419-bd59-308f9ec3bc44 | 1376389800
>  685bb9ff-a4fe-4e47-95eb-f6a353d9e179 | 1376390400
> cqlsh:dbsite> alter table testint alter bestof TYPE int;
> cqlsh:dbsite> select * from testint ;
>  id                                   | bestof
> --------------------------------------+-----------------------------
>  a848f832-5ded-4ef7-bf4b-7db561564c57 |  '\x00\x00\x00\x00R\n\x0fX'
>  49d30f84-a409-4433-ad60-eb9c1a06b7bb |     '\x00\x00\x00\x00R\n2^'
>  6cab4798-ad29-4419-bd59-308f9ec3bc44 | '\x00\x00\x00\x00R\n\n\xa8'
>  685bb9ff-a4fe-4e47-95eb-f6a353d9e179 | '\x00\x00\x00\x00R\n\r\x00'
> Failed to decode value '\x00\x00\x00\x00R\n\x0fX' (for column 'bestof') as int: unpack
requires a string argument of length 4
> Failed to decode value '\x00\x00\x00\x00R\n2^' (for column 'bestof') as int: unpack requires
a string argument of length 4
> 2 more decoding errors suppressed.
> I realize that going from BIGINT to INT would cause overflow if a column contained a
number larger than 2^31-1, it is at least technically possible to go in the other direction.
 I also understand that rewriting all the data in the correct format would be a very expensive
operation on a large column family, but if that's not something we want to allow we should
explicitly disallow changing data types if the table has any rows.

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

Mime
View raw message