[
https://issues.apache.org/jira/browse/CASSANDRA-11617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15249832#comment-15249832
]
Sam Tunnicliffe commented on CASSANDRA-11617:
---------------------------------------------
Sure. I mentioned on CASSANDRA-11310 and CASSANDRA-11043 (from where this
ticket came) that we could and should do what you're suggesting, just that we
need to do it with consideration, rather than as an accidental side-effect of
some other change (or bug). We already found 1 place where an assumption about
the command caused a regression, which wasn't covered by any existing tests
(see [this
comment|https://issues.apache.org/jira/browse/CASSANDRA-11310?focusedCommentId=15245922&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15245922])
so I'm just preaching caution wrt the C* codebase itself and any custom index
impls in the wild.
> The presence of custom index expressions doesn't set the indexing flag in
> StatementRestrictions
> -----------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-11617
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11617
> Project: Cassandra
> Issue Type: Bug
> Components: CQL
> Reporter: Sam Tunnicliffe
> Assignee: Sam Tunnicliffe
> Fix For: 3.0.x, 3.x
>
>
> This can lead to queries with index expressions being executed as single
> partition rather than partition range reads, which should always be the case
> for index queries, even when the partition key is restricted.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
