[jira] [Updated] (CASSANDRA-5164) Invalid streamId in cql binary protocol when using invalid CL
[ https://issues.apache.org/jira/browse/CASSANDRA-5164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Chalamet updated CASSANDRA-5164: --- Attachment: 5164-2.txt fix invalid cast Invalid streamId in cql binary protocol when using invalid CL - Key: CASSANDRA-5164 URL: https://issues.apache.org/jira/browse/CASSANDRA-5164 Project: Cassandra Issue Type: Bug Components: API Affects Versions: 1.2.0 Environment: Windows 8, java version 1.6.0_37 x86 Reporter: Pierre Chalamet Assignee: Sylvain Lebresne Priority: Minor Fix For: 1.2.4 Attachments: 5164-2.txt, 5164.txt Execute a query using invalid CL (0x100 for example) The response comes but does not use the request streamId (always 0). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CASSANDRA-5164) Invalid streamId in cql binary protocol when using invalid CL
[ https://issues.apache.org/jira/browse/CASSANDRA-5164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylvain Lebresne updated CASSANDRA-5164: Attachment: 5164.txt Attaching patch to preserve the streamId in that case. I note that we don't do any effort to preserve the streamId if you screw up the frame format, but imo it's fair game. If you don't respect the protocol at that level, you have other problems to worry about than the streamId. Invalid streamId in cql binary protocol when using invalid CL - Key: CASSANDRA-5164 URL: https://issues.apache.org/jira/browse/CASSANDRA-5164 Project: Cassandra Issue Type: Bug Components: API Affects Versions: 1.2.0 Environment: Windows 8, java version 1.6.0_37 x86 Reporter: Pierre Chalamet Assignee: Sylvain Lebresne Priority: Minor Fix For: 1.2.4 Attachments: 5164.txt Execute a query using invalid CL (0x100 for example) The response comes but does not use the request streamId (always 0). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CASSANDRA-5164) Invalid streamId in cql binary protocol when using invalid CL
[ https://issues.apache.org/jira/browse/CASSANDRA-5164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Ellis updated CASSANDRA-5164: -- Reviewer: pchalamet Invalid streamId in cql binary protocol when using invalid CL - Key: CASSANDRA-5164 URL: https://issues.apache.org/jira/browse/CASSANDRA-5164 Project: Cassandra Issue Type: Bug Components: API Affects Versions: 1.2.0 Environment: Windows 8, java version 1.6.0_37 x86 Reporter: Pierre Chalamet Assignee: Sylvain Lebresne Priority: Minor Fix For: 1.2.4 Attachments: 5164.txt Execute a query using invalid CL (0x100 for example) The response comes but does not use the request streamId (always 0). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CASSANDRA-5164) Invalid streamId in cql binary protocol when using invalid CL
[ https://issues.apache.org/jira/browse/CASSANDRA-5164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Ellis updated CASSANDRA-5164: -- Component/s: API Fix Version/s: 1.2.4 Assignee: Sylvain Lebresne Invalid streamId in cql binary protocol when using invalid CL - Key: CASSANDRA-5164 URL: https://issues.apache.org/jira/browse/CASSANDRA-5164 Project: Cassandra Issue Type: Bug Components: API Affects Versions: 1.2.0 Environment: Windows 8, java version 1.6.0_37 x86 Reporter: Pierre Chalamet Assignee: Sylvain Lebresne Priority: Minor Fix For: 1.2.4 Execute a query using invalid CL (0x100 for example) The response comes but does not use the request streamId (always 0). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
