cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <j...@apache.org>
Subject [jira] Assigned: (CASSANDRA-1145) Reading with CL > ONE returns multiple copies of the same column per key.
Date Wed, 16 Jun 2010 21:26:26 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-1145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jonathan Ellis reassigned CASSANDRA-1145:
-----------------------------------------

    Assignee: Jeremy Hanna

Joost: :) no, it really is a bug

Jeremy: could you have a look?

> 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.3
>
>         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.


Mime
View raw message