[
https://issues.apache.org/jira/browse/CASSANDRA-15933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17164528#comment-17164528
]
Alex Petrov commented on CASSANDRA-15933:
-----------------------------------------
+1
The only think I would add is a test with a table that has a type that
indirectly references altered type, and same with the nested collection, like
that:
{code}
String type2 = createType("CREATE TYPE %s (v1 frozen<" + type + ">, v2 frozen<"
+ type + ">)");
String table = createTable("CREATE TABLE %s (pk frozen<" + type2 + ">, val int,
PRIMARY KEY(pk));");
{code}
and
{code}
String type = createType("CREATE TYPE %s (v1 int)");
String table = createTable("CREATE TABLE %s (pk frozen<list<frozen<" + type +
">>>, val int, PRIMARY KEY(pk));");
{code}
> 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: [email protected]
For additional commands, e-mail: [email protected]
