cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aleksey Yeschenko (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-7056) Add RAMP transactions
Date Wed, 09 Jul 2014 11:09:06 GMT

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

Aleksey Yeschenko commented on CASSANDRA-7056:
----------------------------------------------

bq.  (with logged commit so we don't need to rely purely on "read repair" for coordinator
failure mid-commit)

Right, with logged commit. I was assuming (hoping, really), that this would replace what we
currently have, not merely extend it. But, yes, with logged commit we can "replace" the batchlog
for the purposes of triggers.

I'd also vote for making UNLOGGED the default (implicit) BATCH behavior, now that the LOGGED
batches would cost even more than they do now.

> Add RAMP transactions
> ---------------------
>
>                 Key: CASSANDRA-7056
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-7056
>             Project: Cassandra
>          Issue Type: Wish
>          Components: Core
>            Reporter: Tupshin Harper
>            Priority: Minor
>
> We should take a look at [RAMP|http://www.bailis.org/blog/scalable-atomic-visibility-with-ramp-transactions/]
transactions, and figure out if they can be used to provide more efficient LWT (or LWT-like)
operations.



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

Mime
View raw message