cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kelvin Kakugawa (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CASSANDRA-1502) remove IClock from internals
Date Sat, 18 Sep 2010 23:32:34 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-1502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12911117#action_12911117
] 

Kelvin Kakugawa commented on CASSANDRA-1502:
--------------------------------------------

Refactoring CASSANDRA-1072's logic into a new kind of Column will not result in a cleaner
design.  This approach is manageable for relatively small customizations, e.g. expiring columns
because it touches only one method, but it's definitely harder to grok when it's all inlined
into a single class.  i.e., column and clock logic will all be in one place, now.  The only
benefit will be that it encapsulates all of the Column modifications into a single class.

Potential problem areas include:
- reconciliation (CF's addColumn)
- deletion
- repair (cleanContext)
- interface transformations (transforming the value from the external to internal format)
- context manipulations (modifying it to operation on value, instead of timestamp / clock)

However, I am sure that I'm missing details.

> remove IClock from internals
> ----------------------------
>
>                 Key: CASSANDRA-1502
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-1502
>             Project: Cassandra
>          Issue Type: Task
>          Components: Core
>    Affects Versions: 0.7 beta 1
>            Reporter: Jonathan Ellis
>             Fix For: 0.7.0
>
>
> finish what CASSANDRA-1501 started (i.e., finish reverting CASSANDRA-1070)

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


Mime
View raw message