cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eric Evans (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-3031) Add 4 byte integer type
Date Sat, 03 Sep 2011 15:38:09 GMT

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

Eric Evans commented on CASSANDRA-3031:
---------------------------------------

{quote}
with this patch applied new CF created via cqlsh are using new org.apache.cassandra.db.marshal.IntType
type for int columns. Old applications using CF created with old int type are unaffected.
In python returned type to old apps is int or long depending on value inserted. Patch is fully
backward compatible, i havent discovered any incompatibility yet.
{quote}

It is true that drivers should do the right thing insofar as they will continue to see LongType
schema and deserialize the 8 byte values to whatever makes sense. However, an expectation
is still being broken, and it's hard to imagine all of the cases where this will blow up someones
face.

Imagine someone that uses a schema written as CQL to setup new nodes.  Depending on the version
it is applied to, they're going to get entirely different and incompatible schemas.

> Add 4 byte integer type
> -----------------------
>
>                 Key: CASSANDRA-3031
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-3031
>             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
too.
> 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 
> http://comments.gmane.org/gmane.comp.db.hector.user/2125
> https://issues.apache.org/jira/browse/CASSANDRA-2585
> 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: http://www.atlassian.com/software/jira

        

Mime
View raw message