[
https://issues.apache.org/jira/browse/CASSANDRA-6377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15182801#comment-15182801
]
Benjamin Lerer commented on CASSANDRA-6377:
-------------------------------------------
I realize that there is a bit of misscommunication from my part regarding this
ticket. The committed patches fix only the behavior for filering on non-primary
key columns.
My intent was to fix the behaviour for this type of queries because we were
supporting it already partially. It is the main reason why the patch made it to
3.0.5 and 3.5 (which are bug fix releases).
Sorry, for not communicating it properly.
I have open CASSANDRA-11310 for dealing with filtering on clustering columns.
> ALLOW FILTERING should allow seq scan filtering
> -----------------------------------------------
>
> Key: CASSANDRA-6377
> URL: https://issues.apache.org/jira/browse/CASSANDRA-6377
> Project: Cassandra
> Issue Type: Improvement
> Components: CQL
> Reporter: Jonathan Ellis
> Assignee: Benjamin Lerer
> Labels: cql
> Fix For: 2.2.6, 3.5, 3.0.5
>
>
> CREATE TABLE emp_table2 (
> empID int PRIMARY KEY,
> firstname text,
> lastname text,
> b_mon text,
> b_day text,
> b_yr text,
> );
> INSERT INTO emp_table2 (empID,firstname,lastname,b_mon,b_day,b_yr)
> VALUES (100,'jane','doe','oct','31','1980');
> INSERT INTO emp_table2 (empID,firstname,lastname,b_mon,b_day,b_yr)
> VALUES (101,'john','smith','jan','01','1981');
> INSERT INTO emp_table2 (empID,firstname,lastname,b_mon,b_day,b_yr)
> VALUES (102,'mary','jones','apr','15','1982');
> INSERT INTO emp_table2 (empID,firstname,lastname,b_mon,b_day,b_yr)
> VALUES (103,'tim','best','oct','25','1982');
>
> SELECT b_mon,b_day,b_yr,firstname,lastname FROM emp_table2
> WHERE b_mon='oct' ALLOW FILTERING;
> Bad Request: No indexed columns present in by-columns clause with Equal
> operator
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
