cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eric Evans (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-3031) Add 4 byte integer type
Date Tue, 06 Sep 2011 12:16:09 GMT


Eric Evans commented on CASSANDRA-3031:

I hate to do that because of the WTF-inducement that will have on novices. CQL is young enough
that we should be trying to optimize for the thousands of people who have never tried it yet,
not the tens of people (being generous) who have used it in a real system. Calling [the original
CQL API released in 0.8] 1.0 instead of 0.1 doesn't change that.

Having explicitly sized integer types seemed interesting to me either way, I don't have strong
feelings about what to do with int, but doesn't default in to varint also violate the element
of least-surprise.

As far as versioning goes, I'm pretty much a hard -1 if the suggestion is that we sneak in
a change like this without updating the language version accordingly.  But I would accept
that a bump from 1.x to 2.x coinciding with the release of Cassandra 1.0 makes sense if there
are some nits that people would rather not wait on.

> Add 4 byte integer type
> -----------------------
>                 Key: CASSANDRA-3031
>                 URL:
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>    Affects Versions: 0.8.4
>         Environment: any
>            Reporter: Radim Kolar
>            Priority: Minor
>              Labels: hector, lhf
>             Fix For: 1.0
>         Attachments: apache-cassandra-0.8.4-SNAPSHOT.jar, src.diff, test.diff
> 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