[
https://issues.apache.org/jira/browse/CASSANDRA-7056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14046914#comment-14046914
]
Benedict commented on CASSANDRA-7056:
-------------------------------------
I can say that, from the point of view of a prior target consumer, the addition
of cross-cluster consistent reads would have been exciting for me.
On implementation details, thinking more from the point of view of my prior
self, I would love to see this support streamed batches of arbitrary size. By
which I mean I would have liked to start a write transaction, stream arbitrary
amounts of data, and have it commit with complete isolation or not. To this
end, I'm leaning towards writing the data straight into the memtables, but
maintain a separate set of "uncommitted" transaction ids, which can be filtered
out at read time. If a record is overwritten either before or after it is
committed, it is moved to the read-buffer. I doubt this will be dramatically
more complex, but the approach to implementation is fundamentally different. It
seems to me supporting transactions of arbitrary size is an equally powerful
win to consistent transactions.
> 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)
