[
https://issues.apache.org/jira/browse/CASSANDRA-11310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15223225#comment-15223225
]
Alex Petrov commented on CASSANDRA-11310:
-----------------------------------------
I've found one problem. It turns out that the restrictions I specified were a
bit too strict and under several scenarios (for example, when PK is restricted
with EQ and there are two slices, although both slices have same first column)
were involving filtering even though they shouldn't have. One other scenario
was handled incorrectly because the position counter was never updated.
With Frozen collection tests - it's just missed cases that previously were
disallowed.
I've pushed (unsquashed to make it easier to trace changes) commits here:
https://github.com/ifesdjeen/cassandra/commits/11310-trunk
> 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)
