You can also subdivide hourly partition further by adding an artificial
"bucket" field to the partition key, which you populate with a random
number say between 0 and 10. When you query, you fan out 10 queries, one
for each bucket, and you need to do a manual merge of the resilts. This way
you pay
11).
On Wed, Nov 11, 2015 at 2:31 PM, Tyler Hobbs wrote:
> 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-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
