https://github.com/rantav/hector/issues#issue/126
and the following thrift issue seems related:
https://issues.apache.org/jira/browse/THRIFT-773
I guess we could force number types to BigInteger, but I'm afraid
there might be deeper issues. Thoughts?
On Wed, Jan 19, 2011 at 12:05 PM, tcn <timo.n...@gmail.com> wrote:
> On Jan 19, 6:07 pm, Nate McCall <n...@riptano.com> wrote:
>> If it is local, that is the best way.
>
> I meant you guys :)
>
> So, this one behaves weird:
>
> .addInsertion(now, cf, createColumn("rc", 256, SS, new
> IntegerSerializer())).execute();
>
> which serializes to [0,0,1,0], i.e little endian.
>
> This one works perfectly:
>
> .addInsertion(now, cf, createColumn("rc", new String(new
> BigInteger("256").toByteArray()), SS, SS)).execute();
>
> which serializes to [1,0], i.e. big endian and no padding of zeros.
>
> This is where my knowledge about thrift/cassandra/hector ends. I saw
> that the IntegerType of cassandra uses BigInteger.toByteBuffer which
> serializes big endian. When googling for thrift endian you find
> THRIFT-773.
>
> For somebody who knows cassandra and its code base better than me it
> should be much easier to figure out what's going on.
>