cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sylvain Lebresne (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-7413) Native Protocol V3 CREATE Response
Date Thu, 19 Jun 2014 12:17:24 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-7413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Sylvain Lebresne updated CASSANDRA-7413:
----------------------------------------

    Attachment: 7413.txt

It's an oversight. There is no reason to do a difference between the response we send on a
schema change, and the schema change event. Attaching simple patch to fix the discrepancy
(the patch makes sure we reuse the same code in both case too so we don't have to update 2
places next time we change something).

> 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
>             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)

Mime
View raw message