[
https://issues.apache.org/jira/browse/CASSANDRA-7342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14028420#comment-14028420
]
sankalp kohli edited comment on CASSANDRA-7342 at 6/11/14 9:30 PM:
---
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, //New Column
PRIMARY KEY (target_id, hint_id, message_version);
was (Author: kohlisankalp):
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)
