You CAN only supply some of the components for a slice.
On Fri, Dec 20, 2013 at 2:13 PM, Josh Dzielak wrote:
> Is there a way to include *multiple* column names in a slice query where
> one only component of the composite column name key needs to match?
>
> For example, if this was a single ro
Thanks Nate.
I will take a look at extending thrift, seems like this could be useful for
some folks.
On Friday, December 20, 2013 at 12:29 PM, Nate McCall wrote:
> >
> > My questions –
> >
> > 1) Is this supported in the Thrift interface or CQL?
>
> Not directly, no.
>
> > 2) If
>
>
> My questions –
>
> 1) Is this supported in the Thrift interface or CQL?
>
Not directly, no.
> 2) If not, is there clever data modeling or indexing that could accomplish
> this use case? 1 single-row round-trip to get these columns?
>
If this is a query done frequently you could prefix bot
Is there a way to include *multiple* column names in a slice query where one
only component of the composite column name key needs to match?
For example, if this was a single row -
username:0 | username:1 | city:0 | city:1 | other:0|
other:1
-
