GitHub user jegonzal opened a pull request:

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

    [SPARK-3650] Fix TriangleCount handling of reverse edges

    This PR causes the TriangleCount algorithm to remove self-edges, direct 
edges from low-id to high-id (canonical direction), and then remove duplicate 
edges, before running the triangle count algorithm.
    


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

    $ git pull https://github.com/jegonzal/spark FixTriangleCount

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

    https://github.com/apache/spark/pull/2495.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 #2495
    
----
commit daf1ab5e66259d0af449a91ca7c230323ac49daa
Author: Joseph E. Gonzalez <[email protected]>
Date:   2014-09-22T21:57:28Z

    Improving Triangle Count

commit d054d33181486e3b90222e5e30b2f20648434673
Author: Joseph E. Gonzalez <[email protected]>
Date:   2014-09-22T22:16:46Z

    fixing bug in unit tests where bi-directed edges lead to duplicate 
triangles.

----


---
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