Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Wed, 20 Apr 2016 14:18:25 +0000 (UTC)
From: "Sylvain Lebresne (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12960311.1461154219000.279057.1461161905502@Atlassian.JIRA>
In-Reply-To: <JIRA.12960311.1461154219000@Atlassian.JIRA>
References: <JIRA.12960311.1461154219000@Atlassian.JIRA>
 <JIRA.12960311.1461154219958@arcas>
Subject: [jira] [Commented] (CASSANDRA-11617) The presence of custom index
 expressions doesn't set the indexing flag in StatementRestrictions
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/CASSANDRA-11617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15249971#comment-15249971 ] 

Sylvain Lebresne commented on CASSANDRA-11617:
----------------------------------------------

bq.  just that we need to do it with consideration, rather than as an accidental side-effect of some other change

Of course. But I guess my point is, hasn't it always be the case in 3.x that custom indexes uses {{SinglePartitionReadCommand}}? Because if that's the case, you could argue that changing it could surprise some users and so I question the idea of switch to partition range query now (in 3.0.6/3.6) if we're going to change it back soon enough. Basically I'm suggesting to keep it just for custom index (since again, the change to the 2ndary index API are big enough in 3.x that I'm kind of more interested in keeping consistency in 3.x than trying to get back to pre-3.x behavior), maybe using this ticket to fix the few custom index specific things that are missing (the ones mentioned by [~adelapena]). We can then totally left switching the internal indexes to another ticket, which I definitively agree we'll have to test carefully.

> 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)