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/11/26 03:26:39 UTC

[jira] Resolved: (CASSANDRA-171) avoid sending responses for RowMutations generated by a fire-and-forget insert

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

Jonathan Ellis resolved CASSANDRA-171.
--------------------------------------

    Resolution: Won't Fix

Since the vast majority of inserts are done with at least CL.ONE, adding an optimization for the ZERO case that makes the others (slightly) less efficient seems like the wrong call.

> avoid sending responses for RowMutations generated by a fire-and-forget insert
> ------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-171
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-171
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Jonathan Ellis
>            Priority: Minor
>
> This is not wrong, just inefficient.

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