cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jeremiah Jordan (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-13013) Potential regression from CASSANDRA-6377
Date Fri, 27 Jan 2017 18:11:25 GMT

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

Jeremiah Jordan updated CASSANDRA-13013:
----------------------------------------
    Fix Version/s: 3.10

> Potential regression from CASSANDRA-6377
> ----------------------------------------
>
>                 Key: CASSANDRA-13013
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-13013
>             Project: Cassandra
>          Issue Type: Bug
>          Components: CQL
>            Reporter: Sylvain Lebresne
>            Assignee: Benjamin Lerer
>             Fix For: 3.10
>
>
> As noted by [~thobbs] in CASSANDRA-12768, in 3.0 (and prior) [we return static results|https://github.com/apache/cassandra/blob/cassandra-3.0/src/java/org/apache/cassandra/cql3/statements/SelectStatement.java#L753-L754]
for a partition if it is the only results when the query is a 2ndary index query. This doesn't
seem to happen anymore in 3.X and that was removed by CASSANDRA-6377 (see the [merge commit|https://github.com/apache/cassandra/commit/8c83c8edab4f1c23c382bb0ac076cab44d5f4dda#diff-75ebe654dcf6c8c474f787abaf47bb68L705],
but that removal is actually part of the original [trunk patch for CASSANDRA-6377|https://github.com/blerer/cassandra/commit/e22a311a6d379a9f81668b7995501962ba705380#diff-75ebe654dcf6c8c474f787abaf47bb68L705]).
> The removal looks intentional but it's unclear to [~thobbs] and myself why it's not a
potentially breaking change, and even if it's a legit change, why it was done in 3.X (then
trunk) but not 3.0?
> [~blerer], can you enlighten us?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message