[jira] [Updated] (CASSANDRA-12951) AlterTypeStatement generates potentially huge number of schema announcements, only one of them necessary

["Aleksey Yeschenko (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CASSANDRA-12951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Aleksey Yeschenko updated CASSANDRA-12951:
------------------------------------------
    Component/s: Distributed Metadata

> AlterTypeStatement generates potentially huge number of schema announcements, only one of them necessary
> --------------------------------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-12951
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-12951
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Distributed Metadata
>            Reporter: Aleksey Yeschenko
>            Priority: Minor
>             Fix For: 3.0.x, 3.x
>
>
> Arguably an oversight from my 3.0 schema work. In 3.0 and up we store type names - including UDTs - by their name only in all schema tables, including columns, functions, and other types.
> As such, it's completely redundant to issue a migration for each affected table/function/type, the original type change migration will take care of everything automatically. It's dead and harmful code.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)