[ https://issues.apache.org/jira/browse/CASSANDRA-12443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15626303#comment-15626303 ]
Aleksey Yeschenko commented on CASSANDRA-12443: ----------------------------------------------- FWIW, we do currently serialise the length of each field preceding it in UDTs and Tuples, but I can recall plans to optimise our UDT/tuple encoding on disk to get rid of that extra 4 bytes per field of overhead. While it's not strictly necessary to disable {{ALTER TYPE ALTER TYPE}} right now, we might as well do it now, knowing that we will eventually, and it's not something that really useful anyway. Plus for consistency with {{ALTER TABLE}}. > 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)