cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kelvin Kakugawa (JIRA)" <>
Subject [jira] Updated: (CASSANDRA-580) vector clock support
Date Wed, 06 Jan 2010 02:11:54 GMT


Kelvin Kakugawa updated CASSANDRA-580:

    Attachment: 580-context-v4.patch

Moved utility methods in VersionVectorContext to FBUtilities.
Modified impl to use System.arraycopy().
Modified internal methods to be protected/private (depending on whether necessary for testing).
Removed now unused methods.

Note: FBUtilities.compareByteSubArrays() will throw an IllegalArgumentException if a length
is passed in that extends past either array.

> 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-context-v1.patch, 580-context-v2.patch, 580-context-v3.patch,
580-context-v4.patch, 580-interface-1-add-vector-clock.diff, 580-interface-2-add-vector-clock.diff,
580-thrift-v3.patch, 580-thrift-v4.patch, 580-thrift-v5.patch, 580-thrift-v6.patch
>   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