You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Carl Yeksigian (JIRA)" <ji...@apache.org> on 2016/09/30 15:35:21 UTC

[jira] [Updated] (CASSANDRA-12443) Remove alter type support

     [ https://issues.apache.org/jira/browse/CASSANDRA-12443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Carl Yeksigian updated CASSANDRA-12443:
---------------------------------------
    Fix Version/s:     (was: 4.x)
                   3.0.x
           Status: Patch Available  (was: Open)

The errors in the tests don't reproduce locally, but I've rebased and pushed a new version and kicked off CI.

Also pushed a new [dtest branch|https://github.com/carlyeks/cassandra-dtest/tree/fix-12443] which removes the alter type statements in those tests as well.

> 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: 3.0.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)