cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tyler Hobbs (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-7617) UDT schema change messages are indistinguishable from table schema changes
Date Thu, 24 Jul 2014 21:56:38 GMT

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

Tyler Hobbs updated CASSANDRA-7617:
-----------------------------------

    Attachment: 7617.txt

7617.txt (and [branch|https://github.com/thobbs/cassandra/tree/CASSANDRA-7617]) uses "keyspace
updated" messages for UDT changes when using the v1 or v2 protocol.  I also updated the docs
for the v1 and v2 protocols to mention the behavior for UDT changes.

> 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)

Mime
View raw message