cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christoph Hack (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-4737) doc/native_protocol.txt isn't up to date
Date Mon, 01 Oct 2012 12:27:07 GMT

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

Christoph Hack commented on CASSANDRA-4737:
-------------------------------------------

Thanks for looking into this. Unfortunately, the specification is still wrong in my opinion:

[short]        A 2 bytes unsigned integer
[short bytes]  A [short] n, followed by n bytes if n >= 0. If n < 0, no byte should
follow and the value represented is `null`.

I'm not entirely sure how I should represent those n<0 using an unsigned integer.
                
> doc/native_protocol.txt isn't up to date
> ----------------------------------------
>
>                 Key: CASSANDRA-4737
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-4737
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Christoph Hack
>            Assignee: Sylvain Lebresne
>            Priority: Trivial
>              Labels: binary_protocol
>             Fix For: 1.2.0 beta 2
>
>
> CASSANDRA-4449 seems to have changed the datatype of the query id returned by a RESULT-PREPARED
message from an {{int}} to a {{short}} n followed by n bytes (representing a md5sum). The
specification at doc/native_protocol.txt doesn't cover this change yet.

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

Mime
View raw message