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 Mon, 05 Sep 2011 07:59:09 GMT

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

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

{quote}
I think that you are worried too much about backward CQL compatibility. Cassandra clusters
are operated by responsible persons and It do not break existing clusters. Fixing schema creating
CQL scripts is trivial (if they exists).
{quote}

It's not idle concern, it's a reaction.

{quote}
Lets say we change CQL int from int8 to int4. It will create new cluster with unexpected schema,
but application will get an exception on first insert, you cant validate int8 in int4 field.
Admin can fix schema via cassandra-cli or fix CQL script. Its fail fast scenario.
{quote}

... and update any code that makes assumptions about the length returned, etc, etc.

Cassandra's next release will be the coveted "1.0", what that means precisely is up to debate,
but I think everyone is in agreement that it communicates We're All Grown Up.  For me, that
means we're past the point were we can realistically suggest that people smoke test, then
pick up any the broken pieces.

> 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