[
https://issues.apache.org/jira/browse/CASSANDRA-11310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15197574#comment-15197574
]
Tyler Hobbs commented on CASSANDRA-11310:
-----------------------------------------
bq. In processClusteringColumnsRestrictions the fact that we set
useSecondaryIndex to true if we allow filtering does not make sense. I am also
not sure why we do it for views (Tyler Hobbs is there a good reason?).
I think you're just asking me about views here, so I'll answer that. The
{{forView}} flag here indicates that it's a internal query used to populate a
view (or subsequently filter individual rows). We're more lenient about what
we'll accept for these internal queries, because the normal performance
implications don't really apply.
> Allow filtering on clustering columns for queries without secondary indexes
> ---------------------------------------------------------------------------
>
> Key: CASSANDRA-11310
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11310
> Project: Cassandra
> Issue Type: Improvement
> Components: CQL
> Reporter: Benjamin Lerer
> Assignee: Alex Petrov
> Labels: doc-impacting
> Fix For: 3.x
>
>
> Since CASSANDRA-6377 queries without index filtering non-primary key columns
> are fully supported.
> It makes sense to also support filtering on clustering-columns.
> {code}
> CREATE TABLE emp_table2 (
> empID int,
> firstname text,
> lastname text,
> b_mon text,
> b_day text,
> b_yr text,
> PRIMARY KEY (empID, b_yr, b_mon, b_day));
> SELECT b_mon,b_day,b_yr,firstname,lastname FROM emp_table2
> WHERE b_mon='oct' ALLOW FILTERING;
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
