[
https://issues.apache.org/jira/browse/CASSANDRA-10721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15130397#comment-15130397
]
Robert Stupp commented on CASSANDRA-10721:
------------------------------------------
Moved the {{referencesUserType}} function to {{AbstractType}}. This is now
effectively a refactoring of the (replaced) {{references}} function to
specifically check the user-type's name. Kicked off the CI tests for 3.0 and
trunk (nothing special in 3.3 and trunk however - just a merge w/o conflicts).
Can you take a look at the latest changes ([complete 3.0 diff is
here|https://github.com/apache/cassandra/compare/20813858297b375e1e3f7f4b09dcba2756f9c58f...snazy:10721-udt-alter-3.0])?
> 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)
