GitHub user viirya opened a pull request:

    https://github.com/apache/spark/pull/11265

    [SPARK-12363][Mllib][Backport-1.3] Remove setRun and fix 
PowerIterationClustering failed test

    ## What changes were proposed in this pull request?
    
    Backport JIRA-SPARK-12363 to branch-1.3.
    
    ## How was the this patch tested?
    
    Unit test.
    
    cc @mengxr 


You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/viirya/spark-1 backport-12363-1.3

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/spark/pull/11265.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 #11265
    
----
commit b86018d5626550d78d119148b65c2c900c22f8ef
Author: Liang-Chi Hsieh <[email protected]>
Date:   2015-12-31T05:28:16Z

    Remove setRun and fix PowerIterationClustering failed test.
    
    Conflicts:
        
mllib/src/main/scala/org/apache/spark/mllib/clustering/PowerIterationClustering.scala

commit 7a3ef5f5a1a6517324730b09dfe80399cfe37a87
Author: Xiangrui Meng <[email protected]>
Date:   2016-02-12T08:32:41Z

    use Graph instead of GraphImpl and update tests and example based on PIC 
paper
    
    Conflicts:
        
examples/src/main/scala/org/apache/spark/examples/mllib/PowerIterationClusteringExample.scala
        
mllib/src/main/scala/org/apache/spark/mllib/clustering/PowerIterationClustering.scala
        
mllib/src/test/scala/org/apache/spark/mllib/clustering/PowerIterationClusteringSuite.scala

----


---
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 [email protected] or file a JIRA ticket
with INFRA.
---

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to