cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jonathan Ellis <jbel...@gmail.com>
Subject Re: MVCC
Date Mon, 03 Aug 2009 17:06:18 GMT
It's there for the same reason as the other timestamps: it lets
cassandra ignore obsolete operations.  So if you do a delete at time X
and an insert at time Y where X < Y, the insert will not be deleted by
mistake even if a node is down temporarily and gets the delete later.

-Jonathan

On Mon, Aug 3, 2009 at 11:59 AM, Mark McBride<mark.mcbride@gmail.com> wrote:
> If this is the case, what does the timestamp passed in to the remove
> call do?  I assumed you had to have it match up with a specific
> version...
>
> On Mon, Aug 3, 2009 at 9:53 AM, <mobiledreamers@gmail.com> wrote:
>> I always thought cassandra had free multiple versions and we needed to
>> manually delete the older versions
>>
>> On Mon, Aug 3, 2009 at 8:56 AM, Jonathan Ellis <jbellis@gmail.com> wrote:
>>>
>>> On Mon, Aug 3, 2009 at 10:49 AM, Jun Rao<junrao@almaden.ibm.com> wrote:
>>> > Ivan,
>>> >
>>> > The original cassandra keeps multiple versions of the column data.
>>>
>>> No, it didn't.  (It had versioning-related bugs but multiple versions
>>> a la Bigtable was never part of the design.)
>>>
>>> -Jonathan
>>
>>
>>
>> --
>> Bidegg worlds best auction site
>> http://bidegg.com
>>
>

Mime
View raw message