GitHub user kmadhugit opened a pull request: https://github.com/apache/spark/pull/7020
Partitionning of an RDD with 0 partition shouldn't yield empty outer join The defaultPartitioner method in org.apache.spark.Partitioner.scala selects the explicitly defined partitioner as the default partitioner, otherwise it selects the partitioner which has more number of partition. Introduced an additional check to select the explicitly defined partitioner only when number of partitions are > 0. This would avoid operators creating null result set You can merge this pull request into a Git repository by running: $ git pull https://github.com/ibmsoe/spark SPARK-8048 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/spark/pull/7020.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #7020 ---- commit cd6472cacf388c9fbe8c8919a3cf48f8090534ee Author: Madhusudanan Kandasamy <madhusuda...@in.ibm.com> Date: 2015-06-25T16:05:19Z Explicit partitionning of an RDD with 0 partition shouldn't yield empty outer join ---- --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. --- --------------------------------------------------------------------- To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org For additional commands, e-mail: reviews-h...@spark.apache.org