[
https://issues.apache.org/jira/browse/CASSANDRA-7413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14038866#comment-14038866
]
Tyler Hobbs commented on CASSANDRA-7413:
----------------------------------------
bq. Why is that? Types are keyspace scoped and you need the keyspace name to
identify a type properly. Or am I misunderstanding what you are suggesting?
The keyspace is already specified earlier in the message (in the same
{{<options>}}, in fact). So, it's redundant and it means you have to split the
string. It also doesn't match the spec.
> 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)
