[
https://issues.apache.org/jira/browse/CASSANDRA-4719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sylvain Lebresne reassigned CASSANDRA-4719:
-------------------------------------------
Assignee: Sylvain Lebresne
> binary protocol: when an invalid event type is watched via a REGISTER
> message, the response message does not have an associated stream id
> -----------------------------------------------------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-4719
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4719
> Project: Cassandra
> Issue Type: Bug
> Components: API
> Affects Versions: 1.2.0 beta 1
> Reporter: paul cannon
> Assignee: Sylvain Lebresne
> Priority: Minor
> Labels: binary_protocol
> Fix For: 1.2.0
>
>
> I tried sending a REGISTER message with an eventlist including the string
> "STATUS_FOO", in order to test error handling in the python driver for that
> eventuality. But the response from the server (a "Server error" with a
> message of "java.lang.IllegalArgumentException: No enum const class
> org.apache.cassandra.transport.Event$Type.STATUS_FOO") had a stream_id of 0,
> so the driver was not able to associate it with the request.
--
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
