cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Carl Yeksigian (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-12443) Remove alter type support
Date Sun, 23 Oct 2016 23:04:58 GMT


Carl Yeksigian commented on CASSANDRA-12443:

I went back and forth on removing the parsing logic from 3.x, but thought that since it wasn't
a major version, it would be better to leave it in and provide a better error message, and
since we have the 4.0 branch, we won't have it hanging around.


Also, it seems like we should bump the CQL version on this, but the next version for 3.0 is
3.4.1, which is already defined in 3.x, and reusing it would cause an inconsistent versioning.
Thoughts, [~blerer]? 

> Remove alter type support
> -------------------------
>                 Key: CASSANDRA-12443
>                 URL:
>             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

View raw message