Mailing-List: contact cassandra-commits-help@incubator.apache.org;
 run by ezmlm
Precedence: bulk
Reply-To: cassandra-dev@incubator.apache.org
Message-ID: <1118165573.1251757892858.JavaMail.jira@brutus>
Date: Mon, 31 Aug 2009 15:31:32 -0700 (PDT)
From: "Jonathan Ellis (JIRA)" <jira@apache.org>
To: cassandra-commits@incubator.apache.org
Subject: [jira] Updated: (CASSANDRA-403) inline BatchMutation struct to make
 batch_insert look more like the rest of the api
In-Reply-To: <874158532.1251757413223.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Jonathan Ellis updated CASSANDRA-403:
-------------------------------------

    Attachment: 403.patch

Getting rid of wrapper structs feels good and will make life better for people using raw Thrift.

When we add CASSANDRA-336 (for 0.5) we will probably add a BatchMutation struct back or something similar to it, for a new method that is to batch_insert what multiget_slice is to get_slice.

> inline BatchMutation struct to make batch_insert look more like the rest of the api
> -----------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-403
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-403
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Jonathan Ellis
>            Assignee: Jonathan Ellis
>         Attachments: 403.patch
>
>
> batch_insert is the only column-oriented method that doesn't take a "string key" argument, because in this case it's combined into BatchMutation.  This violates the principle of least surprise.

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