cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <>
Subject [jira] Commented: (CASSANDRA-1070) Update interface to use a wrapper for various clock types
Date Tue, 25 May 2010 14:04:26 GMT


Jonathan Ellis commented on CASSANDRA-1070:

I think atomicSetMax needs to use compareAndSet to really be correct, or it's still possible
that another thread sets the value to a larger one after our compare but before our getAndSet,
resulting in us still temporarily decreasing the value

> Update interface to use a wrapper for various clock types
> ---------------------------------------------------------
>                 Key: CASSANDRA-1070
>                 URL:
>             Project: Cassandra
>          Issue Type: Sub-task
>          Components: Core
>            Reporter: Johan Oskarsson
>            Assignee: Sylvain Lebresne
>             Fix For: 0.7
>         Attachments: 0001-Introduces-wrapper-for-clock-types-generalizing-time.patch,
0001-v2-Introduces-wrapper-for-clock-types-generalizing-time.patch, 0001-v4-Introduces-wrapper-for-clock-types-generalizing-time.patch,
0001-v5-Introduces-wrapper-for-clock-types-generalizing-time.patch, 0001-v6-Introduces-wrapper-for-clock-types-generalizing-time.patch,
0001-v8-Introduces-wrapper-for-clock-types-generalizing-time.patch, 0002-Update-unit-tests.patch,
0002-v6-Update-unit-tests.patch, 0003-Update-System-tests.patch, 0003-v6-Update-System-tests.patch,
> In the latest CASSANDRA-580 patch the timestamp used for conflict resolution has been
replaced by a Clock object that can contain either timestamp or a context byte array. That
change allows for other conflict resolution techniques to be used. 
> The change can be broken out and submitted here in order to make CASSANDRA-580 more manageable.

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

View raw message