cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benjamin Lerer (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-8418) Queries that require allow filtering are working without it
Date Wed, 10 Dec 2014 21:35:12 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-8418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14241781#comment-14241781
] 

Benjamin Lerer commented on CASSANDRA-8418:
-------------------------------------------

All my apologies. I was wrong the DTest was right. The queries do not need {{ALLOW FILTERING}}
because as {{time1}} is a clustering column the secondary index code can use a {{SliceQueryFilter}}
instead of doing some post filtering on the results returned by the index.

> 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)

Mime
View raw message