Hi all,

I had problems creating a table with composite keys with CQL 3 and accessing it via thrift.

AFAIK the comparators weren't set up in a compatible way. Probably due to betaness of CQL 3.

So I'm now creating and using CFs with Composite Columns exclusively via thrift/Astyanax. Pelops works too.

Astyanax composite help: 
https://github.com/Netflix/astyanax/wiki/Examples - Search for Composite. Beware that the serializer currently doesn't find annotated fields if they are inherited.


On Sat, Aug 18, 2012 at 1:29 AM, Ben Frank <ben@airlust.com> wrote:
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 <Dean.Hiller@nrel.gov> wrote:
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" <greg@named.com> 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).