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/09/01 00:31:32 UTC
[jira] Updated: (CASSANDRA-403) inline BatchMutation struct to make
batch_insert look more like the rest of the api
[ 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.