-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
We don't encode error messages properly for CQL binary protocol #43
Comments
Yeah, I fixed one of these in commit 918b30b. We probably should just go through the CQL binary protocol specification and fix up all of them in one sweep. |
Probably this is related too: On Mon, Jul 27, 2015 at 4:29 PM, Pekka Enberg notifications@github.com
|
@dorlaor Seems unrelated. We don't set |
I sent patches to fix up |
Oh, there's also |
|
This makes cassandra-stress error out like this:
That's because it expects to read consistency level field for
READ_TIMEOUT
error message but we don't write it intransport/server.cc
.Relevant code is in Origin in
org.apache.cassandra.transport.messages.ErrorMessage
.The text was updated successfully, but these errors were encountered: