cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hiller, Dean" <>
Subject (new nosqlOrm linke) composite table with cassandra without using cql3?
Date Mon, 20 Aug 2012 12:28:12 GMT
Sorry, project went through a rename and I didn't realize links changed…

NOTE: You can look for the trick we use to store all longs, ints, shorts as smallest possible
bytes every time.  In fact, a long between –128 and 127 takes up one byte in the value part
and then of course takes up space in the name part.  But overall, it can save lots of space.
 (we do same thing with decimal types).


From: Ben Frank <<>>
Reply-To: "<>" <<>>
Date: Friday, August 17, 2012 5:29 PM
To: "<>" <<>>
Subject: Re: composite table with cassandra without using cql3?

Hi Dean,
   I'm interested in this too, but I get a 404 with the link below, looks like I can't see
your nosqlORM project.


On Thu, Aug 2, 2012 at 9:04 AM, Hiller, Dean <<>>
For how to do it with astyanax, you can see here...

Lines 310 and 335

For how to do with thrift, you could look at astyanax.

I use it on that project for indexing for the ORM layer we use(which is
not listed on the cassandra ORM's page as of yet ;) ).


On 8/2/12 9:50 AM, "Greg Fausak" <<>> wrote:

>I've been using the cql3 to create a composite table.
>Can I use the thrift interface to accomplish the
>same thing?  In other words, do I have to use cql 3 to
>get a composite table type? (The same behavior as
>multiple PRIMARY key columns).

View raw message