Return-Path: X-Original-To: apmail-cassandra-commits-archive@www.apache.org Delivered-To: apmail-cassandra-commits-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 2A1DB11207 for ; Thu, 24 Jul 2014 20:56:40 +0000 (UTC) Received: (qmail 9330 invoked by uid 500); 24 Jul 2014 20:56:40 -0000 Delivered-To: apmail-cassandra-commits-archive@cassandra.apache.org Received: (qmail 9291 invoked by uid 500); 24 Jul 2014 20:56:40 -0000 Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cassandra.apache.org Delivered-To: mailing list commits@cassandra.apache.org Received: (qmail 9278 invoked by uid 99); 24 Jul 2014 20:56:39 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 24 Jul 2014 20:56:39 +0000 Date: Thu, 24 Jul 2014 20:56:39 +0000 (UTC) From: "Tyler Hobbs (JIRA)" To: commits@cassandra.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (CASSANDRA-7617) UDT schema change messages are indistinguishable from table schema changes MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Tyler Hobbs created CASSANDRA-7617: -------------------------------------- Summary: 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 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)