You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@spark.apache.org by "Matei Zaharia (JIRA)" <ji...@apache.org> on 2014/04/24 09:32:14 UTC

[jira] [Resolved] (SPARK-1540) Investigate whether we should require keys in PairRDD to be Comparable

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

Matei Zaharia resolved SPARK-1540.
----------------------------------

    Resolution: Fixed

Resolved here: https://github.com/apache/spark/pull/487/files. We were able to add an implicit Ordering to most methods while giving it a default value of null, which will allow these to work on un-orderble types too using the current, less efficient code path.

> Investigate whether we should require keys in PairRDD to be Comparable
> ----------------------------------------------------------------------
>
>                 Key: SPARK-1540
>                 URL: https://issues.apache.org/jira/browse/SPARK-1540
>             Project: Spark
>          Issue Type: New Feature
>            Reporter: Matei Zaharia
>            Assignee: Matei Zaharia
>            Priority: Blocker
>             Fix For: 1.0.0
>
>
> This is kind of a bigger change, but it would make it easier to do sort-based versions of external operations later. We might also get away without it. Note that sortByKey() already does require an Ordering or Comparables.



--
This message was sent by Atlassian JIRA
(v6.2#6252)