[
https://issues.apache.org/jira/browse/CASSANDRA-7600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tyler Hobbs updated CASSANDRA-7600:
-----------------------------------
Attachment: 7600-2.1.txt
7600-2.0.txt
Agreed, that's the best way to go. The two patches do just that. (Note that
we're skipping 2.1.0 for this.)
[~mishail] do you want to take review on this?
> 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)
