Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Message-ID: <21468708.40211282942316337.JavaMail.jira@thor>
Date: Fri, 27 Aug 2010 16:51:56 -0400 (EDT)
From: "Jon Hermes (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Subject: [jira] Updated: (CASSANDRA-1329) make multiget take a set of keys
 instead of a list
In-Reply-To: <28924078.33021280267364485.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Jon Hermes updated CASSANDRA-1329:
----------------------------------

    Attachment: 1329.txt

Thrift changed, thrift/CassandraServer changed. 
All of the logic just iterates for (byte[] key : keys), so changing a set to a list is unchanged.

> make multiget take a set of keys instead of a list
> --------------------------------------------------
>
>                 Key: CASSANDRA-1329
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-1329
>             Project: Cassandra
>          Issue Type: Task
>          Components: Core
>            Reporter: Jonathan Ellis
>            Assignee: Jon Hermes
>            Priority: Minor
>             Fix For: 0.7 beta 2
>
>         Attachments: 1329.txt
>
>
> this more correctly sets the expectation that the order of keys in that list doesn't matter, and duplicates don't make sense

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