You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Sylvain Lebresne (JIRA)" <ji...@apache.org> on 2010/08/16 16:09:16 UTC
[jira] Updated: (CASSANDRA-1396) Merge SP.mutate() and
SP.mutateBlocking() (but using a writeResponseHandler that is a noop)
[ https://issues.apache.org/jira/browse/CASSANDRA-1396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sylvain Lebresne updated CASSANDRA-1396:
----------------------------------------
Attachment: 1396-Merge-SP.mutate-and-SP.mutateBlocking.patch
The attached patch remove mutate() (and rename mutateBlocking() in mutate()).
For doing so it introduces a new writeResponseHandler for CL.ZERO. This
writeResponseHandler is a singleton object that does nothing (and holds nothing).
Making this easier on the client of writeResponseHandler requires however a bit
of refactoring (the introduction of IWriteResponseHandler for instance)
> Merge SP.mutate() and SP.mutateBlocking() (but using a writeResponseHandler that is a noop)
> -------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-1396
> URL: https://issues.apache.org/jira/browse/CASSANDRA-1396
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Affects Versions: 0.7 beta 1
> Reporter: Sylvain Lebresne
> Assignee: Sylvain Lebresne
> Priority: Minor
> Fix For: 0.7 beta 2
>
> Attachments: 1396-Merge-SP.mutate-and-SP.mutateBlocking.patch
>
>
> The code of mutate() is the one of mutateBlocking() with anything done by the
> WriteResponseHandler removed. This patch proposes to merge those functions
> and create a specific WriteResponseHandler for CL.ZERO that doesn't wait at all
> instead.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.