[
https://issues.apache.org/jira/browse/CASSANDRA-8418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14295866#comment-14295866
]
Benjamin Lerer commented on CASSANDRA-8418:
-------------------------------------------
The problem with the warning log is that unless we specify the query that
should required {{ALLOW FILTERING}} in the message, the warning is a bit
useless. The person who will found the warning will have no clue of which query
triggered the problem.
On the other hand, logging only the first query that should have required
{{ALLOW FILTERING}} is a bit misleading, as it could give the impression that
only one query was causing problem.
I am more in favor of letting 2.1 as it is and documenting the change in the
{{CHANGES.txt}} file for 3.0.
> Queries that require allow filtering are working without it
> -----------------------------------------------------------
>
> Key: CASSANDRA-8418
> URL: https://issues.apache.org/jira/browse/CASSANDRA-8418
> Project: Cassandra
> Issue Type: Bug
> Reporter: Philip Thompson
> Assignee: Benjamin Lerer
> Priority: Minor
> Fix For: 3.0
>
> Attachments: CASSANDRA-8418.txt
>
>
> The trunk dtest {{cql_tests.py:TestCQL.composite_index_with_pk_test}} has
> begun failing after the changes to CASSANDRA-7981.
> With the schema {code}CREATE TABLE blogs (
> blog_id int,
> time1 int,
> time2 int,
> author text,
> content text,
> PRIMARY KEY (blog_id, time1, time2){code}
> and {code}CREATE INDEX ON blogs(author){code}, then the query
> {code}SELECT blog_id, content FROM blogs WHERE time1 > 0 AND
> author='foo'{code} now requires ALLOW FILTERING, but did not before the
> refactor.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
