cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "sankalp kohli (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-7342) CAS writes does not have hint functionality.
Date Wed, 11 Jun 2014 21:31:03 GMT

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

sankalp kohli commented on CASSANDRA-7342:
------------------------------------------

I was thinking of ways to do it. Can we use the same hints CF and add a new column called
cas_commit and save commits there. This way we can distinguish while replaying the logs whether
it is a commit or a normal mutation. 

CREATE TABLE hints (
    target_id uuid,
    hint_id timeuuid,
    message_version int,
    mutation blob,
    cas_commit blob,
    PRIMARY KEY (target_id, hint_id, message_version)
 * ) WITH COMPACT STORAGE;

> CAS writes does not have hint functionality. 
> ---------------------------------------------
>
>                 Key: CASSANDRA-7342
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-7342
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: sankalp kohli
>
> When a dead node comes up, it gets the last commit but not anything which it has missed.

> This reduces the durability of those writes compared to other writes. 



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message