cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <>
Subject [jira] Updated: (CASSANDRA-580) vector clock support
Date Tue, 01 Dec 2009 19:39:20 GMT


Jonathan Ellis updated CASSANDRA-580:

    Attachment: 580-thrift-v3.patch

The reason I switched to favoring server-side-only is because it lets us get by with much
smaller API changes, as in the attached.

Also, why do we need a timestamp in LogicalClock when we have the counter?  I thought the
whole point was to get away from the problems posed by timestamps.

> vector clock support
> --------------------
>                 Key: CASSANDRA-580
>                 URL:
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: Core
>         Environment: N/A
>            Reporter: Kelvin Kakugawa
>            Assignee: Kelvin Kakugawa
>         Attachments: 580-interface-1-add-vector-clock.diff, 580-interface-2-add-vector-clock.diff,
>   Original Estimate: 672h
>  Remaining Estimate: 672h
> Allow a ColumnFamily to be versioned via vector clocks, instead of long timestamps. 
Purpose: enable incr/decr; flexible conflict resolution.

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

View raw message