You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Joseph K. Bradley (JIRA)" <ji...@apache.org> on 2016/04/05 20:03:25 UTC

[jira] [Created] (SPARK-14408) Is RDD.treeAggregate implemented correctly?

Joseph K. Bradley created SPARK-14408:
-----------------------------------------

             Summary: Is RDD.treeAggregate implemented correctly?
                 Key: SPARK-14408
                 URL: https://issues.apache.org/jira/browse/SPARK-14408
             Project: Spark
          Issue Type: Question
          Components: Spark Core
            Reporter: Joseph K. Bradley


**Issue**
In MLlib, we have assumed that {{RDD.treeAggregate}} allows the {{seqOp}} and {{combOp}} functions to modify and return their first argument, just like {{RDD.aggregate}}.  However, it is not documented that way.

I started to add docs to this effect, but then noticed that {{treeAggregate}} uses {{reduceByKey}} and {{reduce}} in its implementation, neither of which technically allows the seq/combOps to modify and return their first arguments.

**Question**: Is the implementation safe, or does it need to be updated?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org