[
https://issues.apache.org/jira/browse/CASSANDRA-4987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14237697#comment-14237697
]
Sylvain Lebresne commented on CASSANDRA-4987:
---------------------------------------------
No, the changes are not trivial and the complexity of doing it on top of the
current engine doesn't clearly balance the benefit. Which is why I think the
proper way to fix this is just to wait for CASSANDRA-8099 that should handle
that cleanly right off the bat. So I'm going to close this as duplicate of
CASSANDRA-8099 for now. If the latter doesn't pan out of any reason, we can
reconsider this separatly but let's hope we won't need to.
> Support more queries when ALLOW FILTERING is used.
> --------------------------------------------------
>
> Key: CASSANDRA-4987
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4987
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Sylvain Lebresne
> Assignee: Rajanarayanan Thottuvaikkatumana
> Labels: cql
> Fix For: 3.0
>
>
> Even after CASSANDRA-4915, there is still a bunch of queries that we don't
> support even if {{ALLOW FILTERING}} is used. Typically, pretty much any
> queries with restriction on a non-primary-key column unless we have one of
> those restriction that is an EQ on an indexed column.
> If {{ALLOW FILTERING}} is used, we could allow those queries out of
> convenience.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
