You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Rohit Rai (JIRA)" <ji...@apache.org> on 2014/05/06 11:24:18 UTC

[jira] [Commented] (CASSANDRA-7100) Regression in 2.0.x - Cql3 reader returns duplicate rows if the cluster column is reversed

    [ https://issues.apache.org/jira/browse/CASSANDRA-7100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13990462#comment-13990462 ] 

Rohit Rai commented on CASSANDRA-7100:
--------------------------------------

[~alexliu68]

I agree CqlRecordReader is better approach... but some people have applications designed using CqlPagingRecordReader and this breaks them in migration. 

So will be better to apply the patch to CPRR so people can upgrade without problem.

> Regression in 2.0.x - Cql3 reader returns duplicate rows if the cluster column is reversed
> ------------------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-7100
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-7100
>             Project: Cassandra
>          Issue Type: Bug
>    Affects Versions: 1.2.6
>            Reporter: Rohit Rai
>            Assignee: Alex Liu
>         Attachments: 7100-2.0-branch.txt
>
>
> To reproduce it,
> cqlsh:test>  select * from wordfreq;
>  title   | occurances | word
> ---------+------------+-------
>  alex123 |          4 |  liu3
>    alex1 |      23456 |  liu2
>   alex10 |         10 | liu10
>   alex12 |         34 |  liu3
>     alex |     123456 |  liu1
>     alex |       1000 |   liu
> CREATE TABLE wordfreq ( title text, word text, occurances int, PRIMARY KEY (title,occurances)) WITH CLUSTERING ORDER by (occurances DESC);
> The hadoop job returns 7 rows instead of 6 rows. 
> I will post a patch soon.



--
This message was sent by Atlassian JIRA
(v6.2#6252)