You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Benjamin Lerer (JIRA)" <ji...@apache.org> on 2014/12/05 08:39:12 UTC

[jira] [Issue Comment Deleted] (CASSANDRA-8418) Queries that require allow filtering are working without it

     [ https://issues.apache.org/jira/browse/CASSANDRA-8418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Benjamin Lerer updated CASSANDRA-8418:
--------------------------------------
    Comment: was deleted

(was: That was my plan but I did not find how to reopen the ticket from my phone. Sorry for that.)

> 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: 2.0.12, 2.1.3
>
>
> 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)