GitHub user anabranch opened a pull request:
https://github.com/apache/spark/pull/8302
Fix Broken Link
Link was broken because it included tick marks.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/anabranch/spark patch-1
Github user viirya commented on the pull request:
https://github.com/apache/spark/pull/8273#issuecomment-132444373
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 this
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8026#issuecomment-13240
Merged build triggered.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8273#issuecomment-13238
Merged build triggered.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8273#issuecomment-13242
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8026#issuecomment-132446424
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8026#issuecomment-132446425
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user chenghao-intel commented on the pull request:
https://github.com/apache/spark/pull/8026#issuecomment-132446390
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 jerryshao commented on the pull request:
https://github.com/apache/spark/pull/8192#issuecomment-132414870
Thanks @vanzin :)
---
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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/8192
---
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8296#issuecomment-132414842
[Test build #41194 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41194/consoleFull)
for PR 8296 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8297#issuecomment-132415135
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8156#issuecomment-132415238
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/8156#issuecomment-132415170
[Test build #41176 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41176/console)
for PR 8156 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8297#issuecomment-132415115
Merged build triggered.
---
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 tdas commented on a diff in the pull request:
https://github.com/apache/spark/pull/8294#discussion_r37373631
--- Diff:
streaming/src/main/scala/org/apache/spark/streaming/scheduler/ReceiverTracker.scala
---
@@ -469,7 +469,7 @@ class ReceiverTracker(ssc:
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/8296#issuecomment-132415166
LGTM
---
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
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/8280#issuecomment-132415200
Let's close this one.
@shivaram can you submit a proper fix for master?
---
If your project is set up for it, you can reply to this email and have your
reply
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8156#issuecomment-132415237
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 yhuai closed the pull request at:
https://github.com/apache/spark/pull/8280
---
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8297#issuecomment-132417896
[Test build #41195 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41195/console)
for PR 8297 at commit
Github user shivaram commented on the pull request:
https://github.com/apache/spark/pull/8297#issuecomment-132417749
Ok cool. I'll merge this first after Jenkins passes and then we can retest
#7833.
---
If your project is set up for it, you can reply to this email and have your
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8297#issuecomment-132417967
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/7883#issuecomment-132419364
Merged build triggered.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7883#issuecomment-132419456
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8266#issuecomment-132426952
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8266#issuecomment-132426940
Merged build triggered.
---
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 viirya commented on a diff in the pull request:
https://github.com/apache/spark/pull/8273#discussion_r37375336
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/datasources/jdbc/JdbcUtils.scala
---
@@ -122,7 +123,15 @@ object JdbcUtils extends Logging {
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8298#issuecomment-132426939
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8273#issuecomment-132427480
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7883#issuecomment-132427461
Merged build triggered.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7883#issuecomment-132427479
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8275#issuecomment-132428113
[Test build #41185 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41185/console)
for PR 8275 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8266#issuecomment-132429348
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/8299#issuecomment-132429375
Merged build triggered.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8299#issuecomment-132429390
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 tdas commented on the pull request:
https://github.com/apache/spark/pull/8237#issuecomment-132429469
Thanks! Appreciate your understanding.
On Tue, Aug 18, 2015 at 7:51 PM, Shan Hu notificati...@github.com wrote:
@tdas https://github.com/tdas Ok, as you
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8266#issuecomment-132429349
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/8294#issuecomment-132430398
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 tdas commented on the pull request:
https://github.com/apache/spark/pull/8294#issuecomment-132430301
Merging this, thanks @zsxwing for finding this issue.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8294#issuecomment-132430401
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/8286
---
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8275#issuecomment-132437841
[Test build #41204 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41204/consoleFull)
for PR 8275 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8300#issuecomment-132439176
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8200#issuecomment-132439852
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/7150#issuecomment-132439897
Merged build triggered.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7150#issuecomment-132439906
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8301#issuecomment-132439893
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8200#issuecomment-132439851
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 shivaram commented on the pull request:
https://github.com/apache/spark/pull/8276#issuecomment-132440650
BTW does this fix SPARK-9302 as well or does that require `struct` support ?
---
If your project is set up for it, you can reply to this email and have your
reply
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8296#issuecomment-132440472
[Test build #41194 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41194/console)
for PR 8296 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8296#issuecomment-132440566
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/8296#issuecomment-132440564
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 andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/8299#issuecomment-132440871
yes, please call it `enabled` instead
---
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
Github user yu-iskw commented on the pull request:
https://github.com/apache/spark/pull/8266#issuecomment-132440833
I open a PR for `ifelse`.
https://issues.apache.org/jira/browse/SPARK-10106
---
If your project is set up for it, you can reply to this email and have your
reply
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8296#issuecomment-132441423
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8268#issuecomment-132441414
Merged build triggered.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7150#issuecomment-132441405
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/8296#issuecomment-132441408
Merged build triggered.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7150#issuecomment-132441407
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/8268#issuecomment-132441422
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8302#issuecomment-132443358
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 yu-iskw commented on the pull request:
https://github.com/apache/spark/pull/8297#issuecomment-132414939
@shivaram could you review it, please? Thank you for your continuous
support.
---
If your project is set up for it, you can reply to this email and have your
reply
GitHub user yu-iskw opened a pull request:
https://github.com/apache/spark/pull/8297
[SparkR][Minor] Get rid of a long line warning
```
R/functions.R:74:1: style: lines should not be more than 100 characters.
jc - callJStatic(org.apache.spark.sql.functions, lit,
Github user shivaram commented on the pull request:
https://github.com/apache/spark/pull/8297#issuecomment-132416477
LGTM. I thought this was a part of some other open PR ?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well.
Github user yu-iskw commented on the pull request:
https://github.com/apache/spark/pull/8297#issuecomment-132417409
Right. However, I thought we should isolate the validation problem for
#7883. So I reverted it on other PR under review.
---
If your project is set up for it, you can
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8294#issuecomment-132417326
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 yhuai commented on the pull request:
https://github.com/apache/spark/pull/8280#issuecomment-132417459
@shivaram Sure. Just updated the JIRA description.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8294#issuecomment-132417314
Merged build triggered.
---
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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/8257
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7883#issuecomment-132426163
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/7883#issuecomment-132426162
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 shivaram commented on the pull request:
https://github.com/apache/spark/pull/7883#issuecomment-132427259
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8273#issuecomment-132427459
Merged build triggered.
---
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 suyanNone closed the pull request at:
https://github.com/apache/spark/pull/8237
---
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8266#issuecomment-132427697
[Test build #41198 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41198/consoleFull)
for PR 8266 at commit
Github user suyanNone commented on the pull request:
https://github.com/apache/spark/pull/8237#issuecomment-132427763
@tdas Ok, as you already discussed before, so let's stay the same.
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8273#issuecomment-132427782
[Test build #41200 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41200/consoleFull)
for PR 8273 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7883#issuecomment-132427809
[Test build #41199 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41199/consoleFull)
for PR 7883 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8168#issuecomment-132427884
**[Test build #1661 timed
out](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/1661/console)**
for PR 8168 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8299#issuecomment-132429593
[Test build #41201 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41201/consoleFull)
for PR 8299 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8294#issuecomment-132430229
[Test build #41196 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41196/console)
for PR 8294 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8026#issuecomment-132430775
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 have this
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8026#issuecomment-132430765
Build triggered.
---
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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/8294
---
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8300#issuecomment-132439680
[Test build #41205 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41205/consoleFull)
for PR 8300 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8295#issuecomment-132439686
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/8295#issuecomment-132439685
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 tmnd1991 opened a pull request:
https://github.com/apache/spark/pull/8301
[SPARK-10105] Add most frequent k parameter to Word2Vec
When training Word2Vec on a really big dataset, it's really hard to
evaluate the right minCount parameter, it would really help having a
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8200#issuecomment-132439795
[Test build #41193 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41193/console)
for PR 8200 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8276#issuecomment-132440142
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8276#issuecomment-132440143
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/8276#issuecomment-132440124
[Test build #41188 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41188/console)
for PR 8276 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7150#issuecomment-132441355
[Test build #41206 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41206/console)
for PR 7150 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8296#issuecomment-132441641
[Test build #41208 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41208/consoleFull)
for PR 8296 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8268#issuecomment-132441614
[Test build #41207 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41207/consoleFull)
for PR 8268 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8273#issuecomment-132441811
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/8273#issuecomment-132441719
[Test build #41200 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41200/console)
for PR 8273 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8273#issuecomment-132441804
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8026#issuecomment-132444085
Merged build triggered.
---
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
601 - 700 of 1166 matches
Mail list logo
