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 the
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
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
Column Query Modeling
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
I'm modeling a new application and considering the use of SuperColumn vs.
Composite Column paradigms. I understand that SuperColumns are discouraged
in new development, but I'm pondering a query where it seems like
SuperColumns might be better suited.
Consider a CF with SuperColumn layout as
