You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Patricio Echague (JIRA)" <ji...@apache.org> on 2011/06/17 19:40:47 UTC
[jira] [Commented] (CASSANDRA-1473) Implement a Cassandra aware
Hadoop mapreduce.Partitioner
[ https://issues.apache.org/jira/browse/CASSANDRA-1473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13051214#comment-13051214 ]
Patricio Echague commented on CASSANDRA-1473:
---------------------------------------------
Stu, is this partitioner a different one that for instance BytesOrderedPartitioner ?
Where should it be plugged in at?
> 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