[
https://issues.apache.org/jira/browse/CASSANDRA-8806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sylvain Lebresne resolved CASSANDRA-8806.
-----------------------------------------
Resolution: Invalid
This is working as expected. The token restriction in this query really has no
bearing on whether we require filtering or not, since for all we know, a token
restriction can still be selecting the whole ring. So this is the same than:
{noformat}
SELECT * FROM test WHERE c > 0;
{noformat}
And what this query does is iterating over all the partition of the database
but only returning those row that have {{c > 0}}. It doesn't really matter that
each partition will be eliminated relatively quickly if it has nothing for {{c
> 0}}, it still is looked at and the result is that even if very little row in
the database match the query, that query may take a very very long time, and
that's exactly the kind of thing {{ALLOW FILTERING}} is here to warn about.
> Some queries with Token restrictions require ALLOW FILTERING and should not
> ---------------------------------------------------------------------------
>
> Key: CASSANDRA-8806
> URL: https://issues.apache.org/jira/browse/CASSANDRA-8806
> Project: Cassandra
> Issue Type: Bug
> Reporter: Benjamin Lerer
> Assignee: Benjamin Lerer
>
> Queries like {{SELECT * FROM test WHERE token(a, b) > token(0, 0) AND c >
> 10}} require ALLOW FILTERING and should not.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
