[
https://issues.apache.org/jira/browse/CASSANDRA-7413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14037608#comment-14037608
]
Tyler Hobbs commented on CASSANDRA-7413:
----------------------------------------
I actually just noticed this yesterday as well.
With this patch, the type name in the type-related events is now
"<ksname>.<typename>". It should just be "typename".
And a couple of minor comments on the patch:
* In the protocol docs, "is the same than for a "SCHEMA CHANGE" event" should
be "is the same as the body for a "SCHEMA CHANGE" event"
* In {{CreateKeyspaceStatement.changeEvent()}}, you accidentally copied a
comment from {{CreateIndexStatement}}
> Native Protocol V3 CREATE Response
> ----------------------------------
>
> Key: CASSANDRA-7413
> URL: https://issues.apache.org/jira/browse/CASSANDRA-7413
> Project: Cassandra
> Issue Type: Task
> Reporter: Robert Stupp
> Assignee: Sylvain Lebresne
> Labels: protocol
> Fix For: 2.1 rc2
>
> Attachments: 7413.txt
>
>
> Native protocol v3 changes the EVENT (opcode 12) SCHEMA_CHANGE to include the
> target type that changed : <change><target><keyspace><name>.
> The RESULT (opcode 8) SCHEMA_CHANGE has the old layout
> (<change><keyspace><table>.
> Is this difference intentional or does the protocol spec needs change for
> RESULT/SCHEMA_CHANGE?
--
This message was sent by Atlassian JIRA
(v6.2#6252)
