Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Fri, 17 Jun 2011 18:10:48 +0000 (UTC)
From: "Jonathan Ellis (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: 
 <1447259408.15860.1308334248151.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (CASSANDRA-1473) Implement a Cassandra aware
 Hadoop mapreduce.Partitioner
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Jonathan Ellis commented on CASSANDRA-1473:
-------------------------------------------

This is a Hadoop partitioner, not a Cassandra partitioner.

http://hadoop.apache.org/common/docs/r0.20.0/api/org/apache/hadoop/mapreduce/Partitioner.html

> Implement a Cassandra aware Hadoop mapreduce.Partitioner
> --------------------------------------------------------
>
>                 Key: CASSANDRA-1473
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-1473
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Hadoop
>            Reporter: Stu Hood
>            Assignee: Patricio Echague
>             Fix For: 1.0
>
>
> When using a IPartitioner that does not sort data in byte order (RandomPartitioner for example) with Cassandra's Hadoop integration, Hadoop is unaware of the output order of the data.
> We can make Hadoop aware of the proper order of the output data by implementing Hadoop's mapreduce.Partitioner interface: then Hadoop will handle sorting all of the data according to Cassandra's IPartitioner, and the writing clients will be able to connect to smaller numbers of Cassandra nodes.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira