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

Internal cleanup for aggregateMessages #3231

Closed

Conversation

ankurdave
Copy link
Contributor

  1. Add EdgeActiveness enum to represent activeness criteria more cleanly than using booleans.
  2. Comments and whitespace.

1. Add EdgeActiveness enum to represent activeness criteria more cleanly
than using booleans.
2. Comments and whitespace.
@SparkQA
Copy link

SparkQA commented Nov 12, 2014

Test build #23273 has started for PR 3231 at commit 3d485c3.

  • This patch merges cleanly.

@SparkQA
Copy link

SparkQA commented Nov 12, 2014

Test build #23273 has finished for PR 3231 at commit 3d485c3.

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

@AmplabJenkins
Copy link

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

@ankurdave
Copy link
Contributor Author

@rxin

@rxin
Copy link
Contributor

rxin commented Nov 12, 2014

Thanks - merging in master & branch-1.2.

@asfgit asfgit closed this in 0402be9 Nov 12, 2014
asfgit pushed a commit that referenced this pull request Nov 12, 2014
1. Add EdgeActiveness enum to represent activeness criteria more cleanly than using booleans.
2. Comments and whitespace.

Author: Ankur Dave <ankurdave@gmail.com>

Closes #3231 from ankurdave/aggregateMessages-followup and squashes the following commits:

3d485c3 [Ankur Dave] Internal cleanup for aggregateMessages

(cherry picked from commit 0402be9)
Signed-off-by: Reynold Xin <rxin@databricks.com>
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.

4 participants