[
https://issues.apache.org/jira/browse/CASSANDRA-12768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Shuler reopened CASSANDRA-12768:
----------------------------------------
This commit appears to have not been merged to the cassandra-3.11 branch, where
3.10 will be released from. Please merge.
{noformat}
(cassandra-3.11)mshuler@hana:~/git/cassandra$ git log ..cassandra-3.0
commit d9b06e8af41c42244f76058641aeecda53a9bf75 (origin/cassandra-3.0,
cassandra-3.0)
Author: Alex Petrov <[email protected]>
Date: Wed Dec 7 16:04:51 2016 +0100
Make distinction between unset row and non-existing partition for LWTs
Patch by Alex Petrov; reviewed by Sylvain Lebresne for CASSANDRA-12964.
commit 3aefe356545bcc2f5c4453e0d9d704bef339a008 (github/cassandra-3.0)
Merge: 95d0b67 0b97c5d
Author: Robert Stupp <[email protected]>
Date: Wed Dec 7 13:08:35 2016 +0100
Merge branch 'cassandra-2.2' into cassandra-3.0
commit 0b97c5d1f717be30a04c59c766465d9c62a4e9ee (origin/cassandra-2.2,
github/cassandra-2.2, cassandra-2.2)
Author: Robert Stupp <[email protected]>
Date: Wed Dec 7 13:06:55 2016 +0100
testall failure in
org.apache.cassandra.cql3.validation.entities.UFTest.testAllNativeTypes
patch by Robert Stupp; reviewed by Alex Petrov for CASSANDRA-12817
commit 95d0b671d1af154eaf1c1e81992c7f3f51469eee
Author: Sylvain Lebresne <[email protected]>
Date: Mon Oct 10 13:36:15 2016 +0200
CQL often queries static columns unnecessarily
patch by Sylvain Lebresne; reviewed by Tyler Hobbs for CASSANDRA-12768
{noformat}
> CQL often queries static columns unnecessarily
> ----------------------------------------------
>
> Key: CASSANDRA-12768
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12768
> Project: Cassandra
> Issue Type: Bug
> Reporter: Sylvain Lebresne
> Assignee: Sylvain Lebresne
> Fix For: 3.0.11, 3.10
>
>
> While looking at CASSANDRA-12694 (which isn't directly related, but some of
> the results in this ticket are explained by this), I realized that CQL was
> always querying static columns even in cases where this is unnecessary.
> More precisely, for reasons long described elsewhere, we have to query all
> the columns for a row (we have optimizations, see CASSANDRA-10657, but they
> don't change that general fact) to be able to distinguish between the case
> where a row doesn't exist from when it exists but has no values for the
> columns selected by the query. *However*, this really only extend to
> "regular" columns (static columns play no role in deciding whether a
> particular row exists or not) but the implementation in 3.x, which is in
> {{ColumnFilter}}, still always query all static columns.
> We shouldn't do that and it's arguably a performance regression from 2.x.
> Which is why I'm tentatively marking this a bug and for the 3.0 line. It's a
> tiny bit scary for 3.0 though so really more asking for other opinions and
> I'd be happy to stick to 3.x.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
