[
https://issues.apache.org/jira/browse/CASSANDRA-11310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sam Tunnicliffe reopened CASSANDRA-11310:
-----------------------------------------
This introduces a significant change in that it causes certain queries using 2i
to now be processed using {{SinglePartitionReadCommand}} and not
{{PartitionRangeReadCommand}} as previously. While this has been mooted for a
while (and indeed there is unused code in {{CassandraSearcher}} in
preparation), we shouldn't introduce it lightly. There are very likely
assumptions baked into C* itself, and quite possibly into custom 2i
implementations, based on the type of the command being executed. For instance,
a query against a SASI index on a clustering column when the PK is restricted
now fails with a {{ClassCastException}} in {{QueryPlan}}. I'm assuming that
this change was unintentional, so I think we should probably revert #11310
while we fix it.
> 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.6
>
>
> 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)
