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/05/13 21:24:46 UTC

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

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: Bug
            Reporter: Jonathan Ellis
             Fix For: 0.4


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.


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

Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
     [ 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.


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

Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/CASSANDRA-171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jonathan Ellis updated CASSANDRA-171:
-------------------------------------

    Fix Version/s:     (was: 0.4)

> 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
>            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.


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

Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/CASSANDRA-171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jonathan Ellis updated CASSANDRA-171:
-------------------------------------

      Priority: Minor  (was: Major)
    Issue Type: Improvement  (was: Bug)

> 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
>            Reporter: Jonathan Ellis
>            Priority: Minor
>             Fix For: 0.4
>
>
> 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.