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/08/26 02:45:59 UTC

[jira] Commented: (CASSANDRA-70) MultiGet

    [ https://issues.apache.org/jira/browse/CASSANDRA-70?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12747722#action_12747722 ] 

Jonathan Ellis commented on CASSANDRA-70:
-----------------------------------------

so having thought about this a lot...  can we leave the single-key versions in?  i think it makes a lot of sense for poor Java users who don't have a fancy client, don't have the language features to make one, and are stuck with thrift.  kinda sucks to make them create List objects for each call.

of course internally it should just translate that to a multiget in CassandraServer and throw the exception if not found.  so it's _almost_ as pure.

> MultiGet
> --------
>
>                 Key: CASSANDRA-70
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-70
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: Core
>    Affects Versions: 0.4
>            Reporter: Jonathan Ellis
>            Assignee: Chris Goffinet
>         Attachments: 0001-CASSANDRA-70-Multiget-interface-changes.patch
>
>
> Avinash is working on a multiget interface (requesting data from multiple keys at once).

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