cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benjamin Lerer (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-12443) Remove alter type support
Date Tue, 25 Oct 2016 16:32:58 GMT


Benjamin Lerer commented on CASSANDRA-12443:

bq. 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, Benjamin Lerer? 

I think we should add the change to the {{3.4.3}} version for 3.X and trunk and do nothing
for the 3.0 branch. [~thobbs] Do you have an other suggestion?

Otherwise, I think that we should also remove the auto completion from {{cqlsh}} for the {{ALTER}}.

> 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