[ https://issues.apache.org/jira/browse/CASSANDRA-8418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14234753#comment-14234753 ]
Sylvain Lebresne commented on CASSANDRA-8418: --------------------------------------------- Let's not just fix tests without having check all currently maintained version and acted appropriatly. I agree that those queries should have required {{ALLOW FILTERING}} however, so let's understand what's wrong with 2.0/2.1 and maybe fix it there. > Query now requiring allow filtering after refactoring > ----------------------------------------------------- > > Key: CASSANDRA-8418 > URL: https://issues.apache.org/jira/browse/CASSANDRA-8418 > Project: Cassandra > Issue Type: Test > Reporter: Philip Thompson > Assignee: Benjamin Lerer > Priority: Minor > Fix For: 3.0 > > > 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)