You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "C. Scott Andreas (JIRA)" <ji...@apache.org> on 2018/11/18 17:54:00 UTC
[jira] [Updated] (CASSANDRA-11872) Don't force
PartitionRangeReadCommand for 2ndary index queries on single partition
[ https://issues.apache.org/jira/browse/CASSANDRA-11872?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
C. Scott Andreas updated CASSANDRA-11872:
-----------------------------------------
Component/s: Secondary Indexes
> Don't force PartitionRangeReadCommand for 2ndary index queries on single partition
> ----------------------------------------------------------------------------------
>
> Key: CASSANDRA-11872
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11872
> Project: Cassandra
> Issue Type: Improvement
> Components: Secondary Indexes
> Reporter: Sylvain Lebresne
> Priority: Minor
> Fix For: 4.x
>
>
> As mentioned multiple times (CASSANDRA-11617, CASSANDRA-11310 and CASSANDRA-11043 at least), we currently force the use of {{PartitionRangeReadCommand}} when a 2ndary index is in use, even if the query is restricted to a single partition. Which is due to technical debt and we should be able to change that after CASSANDRA-8099 and use {{SinglePartitionReadCommand}}, which would be slightly faster and overall more intuitive/logic.
> We mostly need to test carefully that change to make sure we don't break anything.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org