[
https://issues.apache.org/jira/browse/CASSANDRA-12443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15526479#comment-15526479
]
Carl Yeksigian commented on CASSANDRA-12443:
--------------------------------------------
I've pushed a branch for 3.0 (not sure where this should go, but it is a simple
enough patch to roll it forward to trunk). This disallows the changing of
types; I've changed the things that will help CASSANDRA-10309. Only worry with
this solution is that someone could execute an alter statement on a
lower-version cluster machine and change the schema in the table and on some
cluster machines. However, since we say not to touch the schema while operating
in a mixed-version cluster, this shouldn't happen.
[branch|https://github.com/carlyeks/cassandra/tree/ticket/12443/3.0]
[utest|http://cassci.datastax.com/job/carlyeks-ticket-12443-3.0-testall/]
[dtest|http://cassci.datastax.com/job/carlyeks-ticket-12443-3.0-dtest/]
> Remove alter type support
> -------------------------
>
> Key: CASSANDRA-12443
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12443
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Carl Yeksigian
> Assignee: Carl Yeksigian
> Fix For: 4.x
>
>
> Currently, we allow altering of types. However, because we no longer store
> the length for all types anymore, switching from a fixed-width to
> variable-width type causes issues. commitlog playback breaking startup,
> queries currently in flight getting back bad results, and special casing
> required to handle the changes. In addition, this would solve
> CASSANDRA-10309, as there is no possibility of the types changing while an
> SSTableReader is open.
> For fixed-length, compatible types, the alter also doesn't add much over a
> cast, so users could use that in order to retrieve the altered type.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
