[jira] Commented: (CASSANDRA-1145) Reading with CL > ONE returns multiple copies of the same column per key.

["Jeremy Hanna (JIRA)" <ji...@apache.org>]

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

Jeremy Hanna commented on CASSANDRA-1145:
-----------------------------------------

Hi AJ, could you try to replicate it with the latest 0.6 branch just to see if it wasn't fixed by another fix (cassandra-1042)?  Just wondering if it's a the same bug but showing itself in more than one place.

http://svn.apache.org/repos/asf/cassandra/branches/cassandra-0.6/

> Reading with CL > ONE returns multiple copies of the same column per key.
> -------------------------------------------------------------------------
>
>                 Key: CASSANDRA-1145
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-1145
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 0.6.1
>         Environment: ubuntu jaunty
>            Reporter: AJ Slater
>         Attachments: bugtest.py, storage-conf.xml
>
>
> Testing with 0.6-trunk today:
> Reading with CL > ONE returns multiple copies of the same column per key consistent with the replicas queried before return. i.e, for RC=3, a QUORUM read yields 2 copies and an ALL read returns 3.
> This is with pycassa get_range() which is using get_range_slice()
> I see the same behavior with 0.6.1 and 0.6.2 debs
> If my experience is not unique, anyone using get_range_slice is now deluged with duplicate data.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.