Re: is this correct, thrift unportable to CQL3Š.

2013-09-25 Thread Sylvain Lebresne
t;>> Date: Tuesday, September 24, 2013 10:58 AM >>> To: "user@cassandra.apache.org<mailto:user@cassandra.apache.org>" < >>> user@cassandra.apache.org<mailto:user@cassandra.apache.org>> >>> Subject: Re: is this correct, thrift unportable to CQ

Re: is this correct, thrift unportable to CQL3Š.

2013-09-25 Thread Alex Popescu
>> the exception piece. >> >> Thanks much!!! >> Dean >> >> From: Sylvain Lebresne mailto:sylv...@datastax.com >> >> >> Reply-To: "user@cassandra.apache.org<mailto:user@cassandra.apache.org>" < >> user@cassandra.apache.or

Re: is this correct, thrift unportable to CQL3Š.

2013-09-25 Thread Sylvain Lebresne
astax.com>> > Reply-To: "user@cassandra.apache.org<mailto:user@cassandra.apache.org>" < > user@cassandra.apache.org<mailto:user@cassandra.apache.org>> > Date: Tuesday, September 24, 2013 10:58 AM > To: "user@cassandra.apache.org<mailto:user@cassan

Re: is this correct, thrift unportable to CQL3Š.

2013-09-24 Thread Hiller, Dean
;> Date: Tuesday, September 24, 2013 10:58 AM To: "user@cassandra.apache.org<mailto:user@cassandra.apache.org>" mailto:user@cassandra.apache.org>> Subject: Re: is this correct, thrift unportable to CQL3Š. On Tue, Sep 24, 2013 at 6:17 PM, Vikas Goyal mailto:vi...@easility.com>> wrote

Re: is this correct, thrift unportable to CQL3Š.

2013-09-24 Thread Sylvain Lebresne
On Tue, Sep 24, 2013 at 6:17 PM, Vikas Goyal wrote: > Ok. Great. It works for String and Decimal/Float but not for integer data > type.. > i.e,, if I am passing "" to the composite key column which is either text > or float, it works.. > > session.execute(boundStatement.bind(rowkey, "", ByteBuffe

Re: is this correct, thrift unportable to CQL3Š.

2013-09-24 Thread Vikas Goyal
Ok. Great. It works for String and Decimal/Float but not for integer data type.. i.e,, if I am passing "" to the composite key column which is either text or float, it works.. session.execute(boundStatement.bind(rowkey, "", ByteBuffer.wrap(value))); But not working with bigint, int or varint..and

Re: is this correct, thrift unportable to CQL3Š.

2013-09-24 Thread Sylvain Lebresne
> However,we tried missing the value but it didn't work :( > Right, because not providing a value is akin to having a null value (in the CQL3 sense of the term, which is different from what Dean asked about) and null values are not allowed for primary key columns. You could however insert an *empt

Re: is this correct, thrift unportable to CQL3Š.

2013-09-24 Thread Vikas Goyal
Thanks Sylvain, However,we tried missing the value but it didn't work :( So our code is like below where we are using 3 values if colname is not null..else 2 values.. if (key != null) { PreparedStatement statement = session.prepare("INSERT INTO keys.StringIndice (id,

Re: is this correct, thrift unportable to CQL3Š.

2013-09-24 Thread Sylvain Lebresne
Short answer: not, this is not correct. Longer answer: what you call "null" is actually an empty value (which is *not* the same thing, unless you consider an empty string is the same thing than a null string). As it happens, C* always an empty value as a valid value for any type and that's true of

is this correct, thrift unportable to CQL3Š.

2013-09-24 Thread Hiller, Dean
Many applications in thrift use the wide row with composite column name and as an example, let's say golf score for instance and we end up with golf score : pk like so null : pk56 null : pk45 89 : pk90 89: pk87 90: pk101 95: pk17 Notice that there are some who do not have a golf score(zero woul