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-11820) Altering a column's type causes EOF
Date Fri, 20 May 2016 17:38:13 GMT

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

Carl Yeksigian commented on CASSANDRA-11820:
--------------------------------------------

The EOF is because we are reading more data from the file than is there, since we interpret
the data as part of the length (and start reading the next column). When I add another column,
it will continue to read and not be able to interpret the next columns data (I get an ArrayOutOfBoundsException).

After killing C*, it was in a bad state reading the mutation that was written to the commitlog,
so I had to remove the data; if I had left it long enough to reclaim the commitlog, it could
have restarted, even if we could not recover that data.

> Altering a column's type causes EOF
> -----------------------------------
>
>                 Key: CASSANDRA-11820
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-11820
>             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)
> ALTER TABLE test ALTER b TYPE BLOB
> SELECT * FROM test WHERE a = 1
> {code}
> Tried this on 3.0 and trunk, both fail.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message