[
https://issues.apache.org/jira/browse/CASSANDRA-10721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15036184#comment-15036184
]
Robert Stupp commented on CASSANDRA-10721:
------------------------------------------
userTypeUsedBy: right - it's now completely superfluous (and therefore
removed). I've copied the functionality of {{referencesUserType}} from
{{CQL3Type.Raw}} to {{CQL3Type}} and also removed the
{{AbstractType.references()}} method.
Rebased and pushed a commit for the review changes to the branch and triggered
CI for 3.0+trunk versions.
> Altering a UDT might break UDA deserialisation
> ----------------------------------------------
>
> Key: CASSANDRA-10721
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10721
> Project: Cassandra
> Issue Type: Bug
> Components: CQL, Distributed Metadata
> Reporter: Aleksey Yeschenko
> Assignee: Robert Stupp
> Fix For: 3.0.x
>
>
> CASSANDRA-10650 switched UDA's {{initcond}} serialisation in schema to its
> CQL literal. This means that if any particular field is renamed in the UDT,
> or of its type gets changes, we will not be able to parse initcond back.
> We should either:
> 1) Forbid renames and type switches in UDTs that are being used in UDAs, or
> 2) Make sure we alter the UDAs in schema alongside the new UDT at all times
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
