[
https://issues.apache.org/jira/browse/CASSANDRA-6950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14003026#comment-14003026
]
Sylvain Lebresne commented on CASSANDRA-6950:
---------------------------------------------
bq. I'm against changing it for Thrift in 2.0.x. But support it for 2.1, so
long as it's accompanied by a noticeable NEWS.txt entry.
At which point, is there really a point bothering? With thrift, we're in "don't
break stuff for people" mode after all, not "change edge case behavior to be
more logical for the years to come". Besides, I'm still bugged by making a
special case for ReversedType for thrift, it does sound very non-thrift-like to
me, and whether or not it is more logical is debatable imo.
In any case, I tend to agree with Aleksey that no matter what we do for 2.1 we
should preserve the behavior in 2.0, so the currently attached patch stands for
2.0 and I'd prefer we first focus on fixing what's definitively a bug for CQL.
Let's maybe open a separate ticket to debate whether or not changing the thrift
behavior is something we want?
> Secondary index query fails with tc range query when ordered by DESC
> --------------------------------------------------------------------
>
> Key: CASSANDRA-6950
> URL: https://issues.apache.org/jira/browse/CASSANDRA-6950
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Environment: RHEL 6.3 virtual guest,
> apache-cassandra-2.0.6-SNAPSHOT-src.tar.gz from build #284 (also tried with
> 2.0.5 with CASSANDRA-6666 patch custom-applied with same result).
> Reporter: Andre Campeau
> Assignee: Sylvain Lebresne
> Fix For: 2.0.8
>
> Attachments: 6950-pycassa-repro.py, 6950.txt
>
>
> create table test4 ( name text, lname text, tc bigint, record text,
> PRIMARY KEY ((name, lname), tc)) WITH CLUSTERING ORDER BY (tc DESC) AND
> compaction={'class': 'LeveledCompactionStrategy'};
> create index test4_index ON test4(lname);
> Populate it with some data and non-zero tc values, then try:
> select * from test4 where lname='blah' and tc>0 allow filtering;
> And, (0 rows) returned, even though there are rows which should be found.
> When I create the table using CLUSTERING ORDER BY (tc ASC), the above query
> works. Rows are correctly returned based on the range check.
> Tried various combinations but with descending order on tc nothing works.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
