cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tupshin Harper (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-7056) Add RAMP transactions
Date Sat, 28 Jun 2014 16:09:26 GMT

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

Tupshin Harper commented on CASSANDRA-7056:
-------------------------------------------

I also want to point out that [~iamaleksey]'s response to global indexes (CASSANDRA-6477)
was: "I think we should leave it to people's client code. We don't need more complexity on
our read/write paths when this can be done client-side."

That combined with "alternatively, we just don't invent new unnecessary concepts (batch reads)
to justify hypothetical things we could do that nobody asked us for" would leave us with absolutely
no approach to achieve consistent cross-partition consistent indexes through either client
or server-side code.

> 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