cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sylvain Lebresne (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-11872) Don't force PartitionRangeReadCommand for 2ndary index queries on single partition
Date Fri, 27 May 2016 15:22:13 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-11872?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Sylvain Lebresne updated CASSANDRA-11872:
-----------------------------------------
    Issue Type: Improvement  (was: Bug)

> 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
>            Reporter: Sylvain Lebresne
>            Priority: Minor
>             Fix For: 3.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
(v6.3.4#6332)

Mime
View raw message