You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Mikhail Stepura (JIRA)" <ji...@apache.org> on 2014/08/21 20:15:12 UTC
[jira] [Commented] (CASSANDRA-7600) Schema change notifications
sent for no-op DDL statements
[ https://issues.apache.org/jira/browse/CASSANDRA-7600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14105705#comment-14105705 ]
Mikhail Stepura commented on CASSANDRA-7600:
--------------------------------------------
LGTM, +1
> Schema change notifications sent for no-op DDL statements
> ---------------------------------------------------------
>
> Key: CASSANDRA-7600
> URL: https://issues.apache.org/jira/browse/CASSANDRA-7600
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Reporter: Tyler Hobbs
> Assignee: Tyler Hobbs
> Priority: Minor
> Fix For: 2.0.10, 2.1.1
>
> Attachments: 7600-2.0.txt, 7600-2.1.txt
>
>
> When schema changes are made with {{IF \[NOT\] EXISTS}} conditions, we return schema change messages (and push out schema change notifications) even if the {{IF \[NOT\] EXISTS}} condition makes it a no-op.
> This results in extra work for native protocol drivers, which typically wait for schema agreement and refresh their schema metadata when schema changes occur.
--
This message was sent by Atlassian JIRA
(v6.2#6252)