[
https://issues.apache.org/jira/browse/CASSANDRA-1070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sylvain Lebresne updated CASSANDRA-1070:
----------------------------------------
Attachment:
0001-v5-Introduces-wrapper-for-clock-types-generalizing-time.patch
Attached v5 patch correct a bug that Johan pointed out to me.
When initializing the system table, a few column were wrongly inserted
with a timestamp of Long.MIN_VALUE instead of 0.
I've also propagated the ttl fix to avro. It made me realize that it was missing
from the patch for #1109 btw. Do you want me to extract that specific part
and attach a patch to #1109 (I don't know if I can reopen it as it was
commited).
> Update interface to use a wrapper for various clock types
> ---------------------------------------------------------
>
> Key: CASSANDRA-1070
> URL: https://issues.apache.org/jira/browse/CASSANDRA-1070
> 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,
> 0002-Update-unit-tests.patch, 0003-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.
