[jira] [Commented] (CASSANDRA-7617) UDT schema change messages are indistinguishable from table schema changes

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

    [ https://issues.apache.org/jira/browse/CASSANDRA-7617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14074289#comment-14074289 ] 

Aleksey Yeschenko commented on CASSANDRA-7617:
----------------------------------------------

+1

> UDT schema change messages are indistinguishable from table schema changes
> --------------------------------------------------------------------------
>
>                 Key: CASSANDRA-7617
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-7617
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>            Reporter: Tyler Hobbs
>            Assignee: Tyler Hobbs
>             Fix For: 2.1.0
>
>         Attachments: 7617.txt
>
>
> With the v2 protocol, schema change messages (both responses and pushed notifications) for UDT changes are indistinguishable from table changes.  This means that drivers using the v2 protocol may not properly detect type changes.  Additionally, if a table and a UDT share the same name and the UDT is dropped, the driver may interpret this as the table being dropped.
> The best solution seems to be to use "keyspace updated" messages for UDT changes when using the v2 protocol.



--
This message was sent by Atlassian JIRA
(v6.2#6252)