Re: Composite Column Query Modeling

2012-09-16 Thread aaron morton
> I may be missing something, but it looks like you pass multiple keys but > only a singular SlicePredicate My bad. I was probably thinking "multiple gets" but wrote multigets. If Collections don't help maybe you need to support both query types using separate CF's. Or a secondary index for t

Re: Composite Column Query Modeling

2012-09-14 Thread Hiller, Dean
;user@cassandra.apache.org<mailto:user@cassandra.apache.org>" mailto:user@cassandra.apache.org>> Date: Friday, September 14, 2012 9:08 AM To: "user@cassandra.apache.org<mailto:user@cassandra.apache.org>" mailto:user@cassandra.apache.org>> Subject: Re: Comp

Re: Composite Column Query Modeling

2012-09-14 Thread Adam Holmberg
I think what you're describing might give me what I'm after, but I don't see how I can pass different column slices in a multiget call. I may be missing something, but it looks like you pass multiple keys but only a singular SlicePredicate. Please let me know if that's not what you meant. I'm awar

Re: Composite Column Query Modeling

2012-09-14 Thread aaron morton
You _could_ use one wide row and do a multiget against the same row for different column slices. Would be less efficient than a single get against the row. But you could still do big contiguous column slices. You may get some benefit from the collections in CQL 3 http://www.datastax.com/dev/bl