[
https://issues.apache.org/jira/browse/CASSANDRA-11339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15235047#comment-15235047
]
Alex Petrov commented on CASSANDRA-11339:
-----------------------------------------
Thank you for the review!
True, sorry, I misread the initial statement and assumed we allow index
queries.
I've added check for {{usesSecondaryIndex}}, which should cover the rest of
cases. We could check also for {{hasClusteringColumnsRestriction}} but that'd
be redundant if I understand it all correctly. The message is now adjusted to
{code}
SELECT DISTINCT with WHERE clause only supports restriction by partition key
{code}
> WHERE clause in SELECT DISTINCT can be ignored
> ----------------------------------------------
>
> Key: CASSANDRA-11339
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11339
> Project: Cassandra
> Issue Type: Bug
> Components: CQL
> Reporter: Philip Thompson
> Assignee: Alex Petrov
> Fix For: 2.2.x, 3.x
>
> Attachments:
> 0001-Add-validation-for-distinct-queries-disallowing-quer.patch
>
>
> I've tested this out on 2.1-head. I'm not sure if it's the same behavior on
> newer versions.
> For a given table t, with {{PRIMARY KEY (id, v)}} the following two queries
> return the same result:
> {{SELECT DISTINCT id FROM t WHERE v > X ALLOW FILTERING}}
> {{SELECT DISTINCT id FROM t}}
> The WHERE clause in the former is silently ignored, and all id are returned,
> regardless of the value of v in any row.
> It seems like this has been a known issue for a while:
> http://stackoverflow.com/questions/26548788/select-distinct-cql-ignores-where-clause
> However, if we don't support filtering on anything but the partition key, we
> should reject the query, rather than silently dropping the where clause
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
