cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jeremy Hanna (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CASSANDRA-1145) Reading with CL > ONE returns multiple copies of the same column per key.
Date Thu, 05 Aug 2010 13:51:19 GMT

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

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

Yes - I wondered if what I had done would affect other things, such as reverting other changes.
 Thanks.  I could see where the problem was, but wasn't 100% sure where to make the change.
 Sounds like they were sorted correctly wrt to token, which our CollatingIterator needed to
take into account.

I ran the same tests again that could formerly reproduce the problem (with several permutations)
and it fixes the problem.

I also ran `ant test` and `nosetests` to make sure everything else was happy.

+1 from me.

> 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
>            Assignee: Jeremy Hanna
>            Priority: Critical
>             Fix For: 0.6.5
>
>         Attachments: 0001-Added-a-unit-test.patch, 0001-Sort-keys.patch, 1145-v2.txt,
bugtest.py, demo.patch, 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.


Mime
View raw message