cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Bannister (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-8848) Protocol exceptions always use streamID 0
Date Tue, 24 Feb 2015 15:55:04 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-8848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14335025#comment-14335025
] 

Chris Bannister commented on CASSANDRA-8848:
--------------------------------------------

Looks good to me, do you want me to update the patch for trunk to match your changes?

> Protocol exceptions always use streamID 0
> -----------------------------------------
>
>                 Key: CASSANDRA-8848
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-8848
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>            Reporter: Chris Bannister
>            Assignee: Tyler Hobbs
>            Priority: Minor
>             Fix For: 2.0.13, 2.1.4
>
>         Attachments: 8848-2.0.txt, 8848-2.1.txt, trunk-8848.patch
>
>
> When decoding the binary protocol if a ProtocolException is thrown the streamID the request
came in on is lost. This makes it very hard for drivers to correctly handle improper protocol
implementations.
> Included is a test case which sends a frame with version 0x82 and op 0x9 which should
return a ProtocolError indicating that PREPARE should be a client Request not a response.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message