cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sylvain Lebresne (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-11820) Altering a column's type causes EOF
Date Thu, 23 Jun 2016 09:26:16 GMT


Sylvain Lebresne commented on CASSANDRA-11820:

Had a look. The reason this happen is that when deserializing from the sstable, we use the
proper type, but create the deserialized cell using a {{ColumnDefinition}} that has that old
type, so when we re-serialize later for intra-node communication, the wrong type is used and
it breaks during deserialization.

The good news is, nothing is corrupted, it just fails during the processing of the query (and
not even when reading the sstable).

I'll wrote a patch to fix it, but it'll probably be only early next week as I have a few other
stuffs I want to finish this week (I'll make sure this gets in 3.0.8/3.8 in any case).

> Altering a column's type causes EOF
> -----------------------------------
>                 Key: CASSANDRA-11820
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Carl Yeksigian
>             Fix For: 3.0.x, 3.x
> While working on CASSANDRA-10309, I was testing altering columns' types. This series
of operations fails:
> {code}
> CREATE TABLE test (a int PRIMARY KEY, b int)
> INSERT INTO test (a, b) VALUES (1, 1)
> SELECT * FROM test WHERE a = 1
> {code}
> Tried this on 3.0 and trunk, both fail.

This message was sent by Atlassian JIRA

View raw message