Correct, it's a full tuple comparison.
On Wed, Nov 11, 2015 at 1:43 PM, Yuri Shkuro wrote:
> Thanks, Tyler.
>
> I also realized that I misunderstood multi-column restriction. Evidently,
> (a, b) > (x, y) does not imply component-wise restriction (a>x && b>y) in
> CQL, it only implies full tuple
Thanks, Tyler.
I also realized that I misunderstood multi-column restriction. Evidently,
(a, b) > (x, y) does not imply component-wise restriction (a>x && b>y) in
CQL, it only implies full tuple comparison. That explains why my condition
(a, b) > (2, 10) was matching row (2, 11).
On Wed, Nov 11,
This is a known problem with multi-column slices and mixed ASC/DESC
clustering orders. See https://issues.apache.org/jira/browse/CASSANDRA-7281
for details.
On Tue, Nov 10, 2015 at 11:02 PM, Yuri Shkuro wrote:
> According to this blog:
> http://www.datastax.com/dev/blog/a-deep-look-to-the-cql-w
According to this blog:
http://www.datastax.com/dev/blog/a-deep-look-to-the-cql-where-clause
I should be able to do multi-column restrictions on clustering columns, as
in the blog example: WHERE (server, time) >= (‘196.8.0.0’, 12:00) AND
(server, time) <= (‘196.8.255.255’, 14:00)
However, I am ge
