yes it would. Whether next_billing_date is timestamp or date wouldn't make any difference on scanning all partitions. If you want to them to be on the same node, you can use composite key, but there's a trade off. The nodes may get unbalanced, so you have to do the math to figure out if your specific use case would lead to unbalanced nodes.
These kinds of partitioning problems have been around for over 30 yrs, so it's not a problem that will magically go away. In theory, if each partition is small enough the query times "should" be acceptable. Having a few large partitions isn't good in practice regardless of whether it's RDBMS or NoSql https://docs.datastax.com/en/cql/3.1/cql/cql_reference/refCompositePk.html On Fri, Sep 23, 2016 at 7:36 AM, Denis Mikhaylov <[email protected]> wrote: > Thanks, for you answer. > > Wouldn’t simple `select * from subscriptions where next_billing_date = > '2016-10-25’` require full scan of all partitions? > >
