Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[SPARK-3650] Fix TriangleCount handling of reverse edges #2495

Closed
wants to merge 3 commits into from

Conversation

jegonzal
Copy link
Contributor

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.

@SparkQA
Copy link

SparkQA commented Sep 22, 2014

Can one of the admins verify this patch?

@ankurdave
Copy link
Contributor

ok to test

@SparkQA
Copy link

SparkQA commented Sep 22, 2014

QA tests have started for PR 2495 at commit d054d33.

  • This patch merges cleanly.

@SparkQA
Copy link

SparkQA commented Sep 22, 2014

QA tests have finished for PR 2495 at commit d054d33.

  • This patch passes unit tests.
  • This patch merges cleanly.
  • This patch adds no public classes.

@SparkQA
Copy link

SparkQA commented Sep 22, 2014

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/20670/

@jegonzal
Copy link
Contributor Author

What is the status on this patch?

@SparkQA
Copy link

SparkQA commented Nov 13, 2014

Test build #23301 has finished for PR 2495 at commit 0461ed0.

  • This patch passes all tests.
  • This patch merges cleanly.
  • This patch adds no public classes.

@jegonzal
Copy link
Contributor Author

@ankurdave take a look at this when you get a chance.

@jegonzal
Copy link
Contributor Author

@rxin and @ankurdave what is the status on this?

@ankurdave
Copy link
Contributor

Jenkins, retest this please.

@SparkQA
Copy link

SparkQA commented Jan 19, 2015

Test build #25737 has finished for PR 2495 at commit 0461ed0.

  • This patch fails to build.
  • This patch merges cleanly.
  • This patch adds no public classes.

@ankurdave
Copy link
Contributor

@jegonzal I fixed the compile error in jegonzal#3.

@jegonzal
Copy link
Contributor Author

Great! What else needs to be done? There was some discussion about how
this might change the semantics of the triangle count function? Is this
still true?

@ankurdave
Copy link
Contributor

I think it just adds a bit of a slowdown for already-canonicalized graphs, which is probably fine considering how expensive triangle count is anyway.

@pwendell
Copy link
Contributor

pwendell commented Jun 4, 2015

I'd like to close this issue pending further updates.

@asfgit asfgit closed this in 9982d45 Jun 4, 2015
@insidedctm
Copy link
Contributor

@pwendell can this be opened again? As per my discussion on the the JIRA ticket this is an issue that came up on the mailing list recently.

asfgit pushed a commit that referenced this pull request Feb 22, 2016
jegonzal ankurdave please could you review

## What changes were proposed in this pull request?

Reworking of jegonzal PR #2495 to address the issue identified in SPARK-3650. Code amended to use the convertToCanonicalEdges method.

## How was the this patch tested?

Patch was tested using the unit tests created in PR #2495

Author: Robin East <robin.east@xense.co.uk>
Author: Joseph E. Gonzalez <joseph.e.gonzalez@gmail.com>

Closes #11290 from insidedctm/spark-3650.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants