You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Sandeep Tata (JIRA)" <ji...@apache.org> on 2009/05/07 21:28:45 UTC

[jira] Assigned: (CASSANDRA-132) Support session level consistency

     [ https://issues.apache.org/jira/browse/CASSANDRA-132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sandeep Tata reassigned CASSANDRA-132:
--------------------------------------

    Assignee: Sandeep Tata

> Support session level consistency
> ---------------------------------
>
>                 Key: CASSANDRA-132
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-132
>             Project: Cassandra
>          Issue Type: Improvement
>    Affects Versions: trunk
>         Environment: all
>            Reporter: Sandeep Tata
>            Assignee: Sandeep Tata
>             Fix For: trunk
>
>
> Limited session-level consistency: if the client connects to a node and performs operations on rows that are local to that node, we should be able to guarantee read-your-writes consistency. If the session ends because of a failure, and the client has to reconnect, you only provide eventual consistency across the sessions.
> (This is a common practical variation of evantual consistency, see: http://www.allthingsdistributed.com/2008/12/eventually_consistent.html for context.)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.