Github user dbtsai commented on a diff in the pull request:
https://github.com/apache/spark/pull/9386#discussion_r43600052
--- Diff: graphx/src/main/scala/org/apache/spark/graphx/lib/PageRank.scala
---
@@ -202,10 +211,15 @@ object PageRank extends Logging {
// Set the
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9395#issuecomment-152931005
**[Test build #44798 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/44798/consoleFull)**
for PR 9395 at commit
Github user chenghao-intel commented on the pull request:
https://github.com/apache/spark/pull/9399#issuecomment-152930901
Oh, for example: let's say we have the table src (key, value) partition (p1)
For the query like "SELECT value FROM src WHERE key > p1",
And we assume
Github user dbtsai commented on the pull request:
https://github.com/apache/spark/pull/9386#issuecomment-152937577
Seems that the implementation of personalized page rank doesn't follow the
twitter's paper entirely when initializing the initial page rank. In the paper,
only the
Github user calvinjia commented on the pull request:
https://github.com/apache/spark/pull/9395#issuecomment-152938145
@pwendell
It seems like the maven tests failed with:
```
java.lang.IllegalArgumentException: Logging directory specified is not a
directory:
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8760#issuecomment-152945048
**[Test build #44800 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/44800/consoleFull)**
for PR 8760 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9243#issuecomment-152915059
**[Test build #44791 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/44791/consoleFull)**
for PR 9243 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9276#issuecomment-152915853
Merged build started.
---
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
GitHub user nongli opened a pull request:
https://github.com/apache/spark/pull/9404
[SPARK-5354] [SQL] Cached tables should preserve partitioning and ordâ¦
â¦ering.
For cached tables, we can just maintain the partitioning and ordering from
the
source relation.
You
Github user calvinjia commented on the pull request:
https://github.com/apache/spark/pull/9395#issuecomment-152919342
@yhuai Thanks for the retest. I'm not sure if this will go away by
re-running or if there is something up with Jenkins/Spark master branch. It
seems like the current
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8872#issuecomment-152922644
**[Test build #44796 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/44796/consoleFull)**
for PR 8872 at commit
Github user dbtsai commented on a diff in the pull request:
https://github.com/apache/spark/pull/9386#discussion_r4368
--- Diff: graphx/src/main/scala/org/apache/spark/graphx/lib/PageRank.scala
---
@@ -104,17 +104,25 @@ object PageRank extends Logging {
graph:
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9243#issuecomment-152935793
**[Test build #44791 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/44791/consoleFull)**
for PR 9243 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9243#issuecomment-152936194
Test PASSed.
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/9276#issuecomment-152940850
Merged build finished. Test PASSed.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9344#issuecomment-152940857
Merged build finished. Test FAILed.
---
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/9344#issuecomment-152940800
**[Test build #44793 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/44793/consoleFull)**
for PR 9344 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9276#issuecomment-152940621
**[Test build #44792 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/44792/consoleFull)**
for PR 9276 at commit
Github user mwws commented on the pull request:
https://github.com/apache/spark/pull/8760#issuecomment-152943965
Jenkins, retest 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
Github user dbtsai commented on the pull request:
https://github.com/apache/spark/pull/9402#issuecomment-152945194
LGTM. Merged into master. 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 project does
401 - 420 of 420 matches
Mail list logo
