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

[jira] Issue Comment Edited: (CASSANDRA-225) Support mastered writes

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

Jonathan Ellis edited comment on CASSANDRA-225 at 7/28/09 1:47 PM:
-------------------------------------------------------------------

Per Jun and my conversation with Cliff Moon at the hackathon, this is not something we want to pursue in Cassandra.

      was (Author: jbellis):
    Per Jun any my conversation with Cliff Moon at the hackathon, this is not something we want to pursue in Cassandra.
  
> Support mastered writes
> -----------------------
>
>                 Key: CASSANDRA-225
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-225
>             Project: Cassandra
>          Issue Type: New Feature
>    Affects Versions: 0.4
>         Environment: all
>            Reporter: Sandeep Tata
>         Attachments: 225.patch
>
>
> Writes to a row today can be run on any of the replicas that own the row. An additional set of APIs to perform "mastered" writes that funnel through a primary is important if applications have some operations that require higher consistency. Test-and-set is an example of one such operation that requires a higher consistency guarantee.
> To stay true to Cassandra's performance goals, this should be done in a way that does not compromise performance for apps that can deal with lower consistency and never use these APIs. That said, an app that mixes higher consistency calls with lower consistency calls should be careful that they don't operate on the same data.

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