[
https://issues.apache.org/jira/browse/CASSANDRA-15933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17155598#comment-17155598
]
Aleksey Yeschenko edited comment on CASSANDRA-15933 at 7/10/20, 4:59 PM:
-------------------------------------------------------------------------
Closing, as this is only an issue in 3.0, and fixed in 3.11 and 4.0 since
CASSANDRA-7423. The issue in 3.0: altering a type used in a PK of a table
causes lookups for previously written data to fail. This will be addressed by
backporting {{TupleType}} changes from 3.11 to 3.0.
EDIT: in all versions this is a problem if a UDT used frozen in a partition key
is altered, since we primarily treat partition keys as opaque byte buffers
internally, and change in serialization makes previously written data
inaccessible.
was (Author: iamaleksey):
Closing, as this is only an issue in 3.0, and fixed in 3.11 and 4.0 since
CASSANDRA-7423. The issue in 3.0: altering a type used in a PK of a table
causes lookups for previously written data to fail. This will be addressed by
backporting {{TupleType}} changes from 3.11 to 3.0.
> Forbid adding new fields to UDTs used in partition key columns
> --------------------------------------------------------------
>
> Key: CASSANDRA-15933
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15933
> Project: Cassandra
> Issue Type: Bug
> Components: Cluster/Schema
> Reporter: Aleksey Yeschenko
> Assignee: Aleksey Yeschenko
> Priority: Normal
> Fix For: 4.0, 3.0.x, 3.11.x
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
