[
https://issues.apache.org/jira/browse/CASSANDRA-8951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14384157#comment-14384157
]
Sylvain Lebresne commented on CASSANDRA-8951:
---------------------------------------------
I suggest we try to get this in 3.0 because it's reasonably trivial and it'll
allow to add a code in the v4 protocol for this/those types.
bq. Just a note to start the ball rolling with byte-order comparability for
smallint...
I suggest leaving that to whatever patch will change it for other types. I
don't think it makes sense to sense to have a inconsistent (with other current
encoding) encoding of {{smallint}} at least in the native protocol and
bothering with conversion between internal and external encoding in this ticket
doesn't make sense. And once we'll handle the other types, handling
{{smallint}} at the same time will be a completely negligible overhead, so it's
easier to leave that aside for now.
> Add smallint (and possibly byte) type
> -------------------------------------
>
> Key: CASSANDRA-8951
> URL: https://issues.apache.org/jira/browse/CASSANDRA-8951
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Sylvain Lebresne
> Assignee: Benjamin Lerer
> Fix For: 3.0
>
>
> We have {{int}} and {{bigint}}, but we don't have a {{smallint}} (2 bytes). I
> see no reason not to add it. And while we're at it, it doesn't cost much to
> add a {{byte}} type either.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
