cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Igor Hrazdil (JIRA)" <>
Subject [jira] [Issue Comment Edited] (CASSANDRA-3031) Add 4 byte integer type
Date Sat, 10 Sep 2011 20:35:08 GMT


Igor Hrazdil edited comment on CASSANDRA-3031 at 9/10/11 8:33 PM:

Mistake in type name int for CLI, see cli_help.diff

      was (Author: igor.hrazdil):
    Mistake in type name int for CLI.
> Add 4 byte integer type
> -----------------------
>                 Key: CASSANDRA-3031
>                 URL:
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>    Affects Versions: 1.0.0
>         Environment: any
>            Reporter: Radim Kolar
>            Assignee: Radim Kolar
>            Priority: Minor
>              Labels: hector, lhf
>             Fix For: 1.0.0
>         Attachments: apache-cassandra-1.0-dev-SNAPSHOT.jar, apache-cassandra-thrift-1.0-dev-SNAPSHOT.jar,
cli_help.diff, drivers.diff, src.diff, test.diff, test.log
> Cassandra currently lacks support for 4byte fixed size integer data type. 
> Java API Hector and C libcassandra likes to serialize integers as 4 bytes in network
order. Problem is that you cant use cassandra-cli to manipulate stored rows. Compatibility
with other applications using api following cassandra integer encoding standard is problematic
> Because adding new datatype/validator is fairly simple I recommend to add int4 data type.
Compatibility with hector is important because it is most used Java cassandra api and lot
of applications are using it.
> This problem was discussed several times already 
> It would be nice to have compatibility with cassandra-cli and other applications without
rewriting hector apps.

This message is automatically generated by JIRA.
For more information on JIRA, see:


View raw message