Sorry, it seems that I did not provide enough details.
IN restrictions are supported on any clustering key as long as ALL the
previous clustering keys are restricted by an equality restrictions ( = or
IN ).
The only way to have a restriction on a clustering column if a previous one
has been restri
I am still getting the following error when trying to run a query with
non-equal conditions in where clause
Caused by: com.datastax.driver.core.exceptions.InvalidQueryException:
Clustering column "author" cannot be restricted (preceding column "timing"
is restricted by a non-EQ relation)
Here i
Since 2.2, IN restrictions are supported on any partition key or clustering
colum in SELECT statement. For UPDATE and DELETE statement they are
supported since 3.0.
Benjamin
On Tue, Sep 6, 2016 at 11:19 AM, Samba wrote:
> Hi,
>
> I understand, from the documentation, that IN operator is permitt
Hi,
I understand, from the documentation, that IN operator is permitted only on
the last column in partition and/or on the last column in the clustering
key.
I can understand that IN on partition key column being indeterministic but
i wonder why is IN permitted only on one (last) clustering colum
