[
https://issues.apache.org/jira/browse/CASSANDRA-132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Ellis updated CASSANDRA-132:
-------------------------------------
Fix Version/s: (was: 0.4)
0.5
> Support (limited) session level consistency
> -------------------------------------------
>
> Key: CASSANDRA-132
> URL: https://issues.apache.org/jira/browse/CASSANDRA-132
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Environment: all
> Reporter: Sandeep Tata
> Assignee: Sandeep Tata
> Fix For: 0.5
>
> Attachments: CASSANDRA-132-v2.patch, CASSANDRA-132-v3.patch,
> CASSANDRA-132.patch
>
>
> Limited session-level consistency: if the client connects to a node and
> performs operations on rows/keys that are local to that node (in that node's
> key range), we should be able to guarantee read-your-writes consistency. If
> the session ends because of a failure, and the client has to reconnect, there
> are no guarantees across the sessions.
> (This is a common practical variation of eventual consistency, see:
> http://www.allthingsdistributed.com/2008/12/eventually_consistent.html for
> context.)
> Supporting this for a "local" sessions is significantly easier than
> supporting session level consistency when the node does not own the data. A
> non-owning node that is reading values from a remote replica will need to
> either do
> a) quorum reads and writes to guarantee session level read-your-writes
> b) pick at least one node to block on and stick to that node as a "master"
> for the session.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
