cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jorge Bay (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-13527) Protocol [short] is used as unsigned and signed value
Date Fri, 12 May 2017 09:27:04 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-13527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jorge Bay updated CASSANDRA-13527:
----------------------------------
    Labels: client-impacting  (was: )

> Protocol [short] is used as unsigned and signed value
> -----------------------------------------------------
>
>                 Key: CASSANDRA-13527
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-13527
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Jorge Bay
>              Labels: client-impacting
>
> The protocol specification describes {{\[short\]}} as unsigned int16, but then on the
section {{2.3. stream}} it describes it like a signed int16, being {{0x7fff}} the maximum
positive value.
> Additionally, {{\[int\]}} and {{\[long\]}} are signed, making the identifier {{\[short\]}}
somewhat confusing.
> For disambiguation, it would be nice to introduce {{\[ushort\]}} or {{\[unsigned short\]}}
(replacing most entries) and leave {{\[short\]}} as signed value, mainly for stream ids.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org


Mime
View raw message