[
https://issues.apache.org/jira/browse/CASSANDRA-9646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15106619#comment-15106619
]
Sylvain Lebresne commented on CASSANDRA-9646:
---------------------------------------------
[~Stefania] could you write some test equivalent to the
{{pushed_notifications_test.py:TestPushedNotifications.schema_changes_test}}
test you added in the context of CASSANDRA-9961, but one that would run on 2.2
(as that one uses MV) so we can check if this is still a thing in 2.2. I'll
note that CASSANDRA-10932 suggests this isn't a problem at least in 3.0, so
maybe this is now fixed, or maybe the schema changes in 3.0 happened to fix
that.
> Duplicated schema change event for table creation
> -------------------------------------------------
>
> Key: CASSANDRA-9646
> URL: https://issues.apache.org/jira/browse/CASSANDRA-9646
> Project: Cassandra
> Issue Type: Bug
> Components: CQL
> Environment: OSX 10.9
> Reporter: Jorge Bay
> Assignee: Stefania
> Priority: Minor
> Labels: client-impacting
> Fix For: 2.2.x
>
>
> When I create a table (or a function), I'm getting notifications for 2
> changes:
> - Target:"KEYSPACE" and type: "UPDATED"
> - Target: "TABLE" AND type "CREATED".
> I think the first one should not be there. This only occurs with C* 2.2.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
