Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/3883#issuecomment-143669273
I don't think this PR is going to proceed; do you mind closing this PR?
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user shijinkui closed the pull request at:
https://github.com/apache/spark/pull/3883
---
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
Github user avulanov commented on a diff in the pull request:
https://github.com/apache/spark/pull/3883#discussion_r35621506
--- Diff: graphx/src/main/scala/org/apache/spark/graphx/Pregel.scala ---
@@ -158,4 +159,91 @@ object Pregel extends Logging {
g
} // end of
Github user avulanov commented on the pull request:
https://github.com/apache/spark/pull/3883#issuecomment-125488842
Do you plan to write tests for the new Pregel API?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If
Github user avulanov commented on a diff in the pull request:
https://github.com/apache/spark/pull/3883#discussion_r35625660
--- Diff: graphx/src/main/scala/org/apache/spark/graphx/Pregel.scala ---
@@ -158,4 +159,91 @@ object Pregel extends Logging {
g
} // end of
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/3883#issuecomment-121073706
Can one of the admins verify this patch?
---
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
Github user shijinkui commented on the pull request:
https://github.com/apache/spark/pull/3883#issuecomment-114688822
cc @andrewor14
---
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/3883#issuecomment-96769883
Can one of the admins verify this patch?
---
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/3883#issuecomment-68973437
[Test build #25132 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/25132/consoleFull)
for PR 3883 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/3883#issuecomment-68972547
[Test build #25129 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/25129/consoleFull)
for PR 3883 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/3883#issuecomment-68972476
[Test build #25129 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/25129/consoleFull)
for PR 3883 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/3883#issuecomment-68972548
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/3883#issuecomment-68977293
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/3883#issuecomment-68977289
[Test build #25132 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/25132/consoleFull)
for PR 3883 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/3883#issuecomment-68972830
[Test build #25131 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/25131/consoleFull)
for PR 3883 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/3883#issuecomment-68972882
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/3883#issuecomment-68972881
[Test build #25131 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/25131/consoleFull)
for PR 3883 at commit
Github user shijinkui commented on the pull request:
https://github.com/apache/spark/pull/3883#issuecomment-68973132
hi, @ankurdave , I remembered that the PR should be as soon as smaller for
easy testing and reviewing.
#3866 is more complexï¼let it independent maybe
Github user ankurdave commented on the pull request:
https://github.com/apache/spark/pull/3883#issuecomment-68904439
@shijinkui Thanks for the PR. Starting from 1.2 we're avoiding any breaking
changes, including this one since it modifies the signature of the Pregel API.
Github user liancheng commented on the pull request:
https://github.com/apache/spark/pull/3883#issuecomment-68638026
ok to test
---
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/3883#issuecomment-68638068
[Test build #25033 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/25033/consoleFull)
for PR 3883 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/3883#issuecomment-68638103
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/3883#issuecomment-68638101
[Test build #25033 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/25033/consoleFull)
for PR 3883 at commit
Github user liancheng commented on the pull request:
https://github.com/apache/spark/pull/3883#issuecomment-68624865
test this please
---
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/3883#issuecomment-68661168
[Test build #25041 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/25041/consoleFull)
for PR 3883 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/3883#issuecomment-68664498
[Test build #25041 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/25041/consoleFull)
for PR 3883 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/3883#issuecomment-68664502
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/3883#issuecomment-68669274
cc @ankurdave can you take a look at this? Thanks.
---
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
GitHub user shijinkui opened a pull request:
https://github.com/apache/spark/pull/3883
[SPARK-5062][Graphx] replace mapReduceTriplets with aggregateMessage in
Pregel Api
since spark 1.2 introduce aggregateMessage instead of mapReduceTriplets, it
improve the performance indeed.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/3883#issuecomment-68578615
Can one of the admins verify this patch?
---
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
30 matches
Mail list logo
