Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8730#issuecomment-139856366
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 srowen commented on the pull request:
https://github.com/apache/spark/pull/8733#issuecomment-139847144
I don't think those are typos. In the first case, a new sentence has not
started. "installation" seems as clear as "installation path" in the second. Do
you mind closing
Github user HyukjinKwon commented on a diff in the pull request:
https://github.com/apache/spark/pull/8391#discussion_r39345066
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/datasources/jdbc/JDBCRDD.scala
---
@@ -275,6 +275,10 @@ private[sql] class JDBCRDD(
Github user zsxwing commented on the pull request:
https://github.com/apache/spark/pull/8710#issuecomment-139849953
> the execution ID is passed directly to the child thread
I believe that this is not the cause of `SPARK-10548`. The cause of
`SPARK-10548` is the child thread
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/8710#issuecomment-139848194
@zsxwing I just noticed a potential source of confusion. If I understand
correctly your view is that we should just clone the properties instead of
having the
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8721#issuecomment-139848193
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 terrytangyuan commented on the pull request:
https://github.com/apache/spark/pull/8733#issuecomment-139858703
You are right. My mistake. Sorry about that.
---
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 terrytangyuan closed the pull request at:
https://github.com/apache/spark/pull/8733
---
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
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/8731
---
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 andrewor14 commented on a diff in the pull request:
https://github.com/apache/spark/pull/8710#discussion_r39345043
--- Diff: core/src/main/scala/org/apache/spark/SparkContext.scala ---
@@ -348,10 +348,24 @@ class SparkContext(config: SparkConf) extends Logging
with
Github user andrewor14 commented on a diff in the pull request:
https://github.com/apache/spark/pull/8710#discussion_r39345154
--- Diff: core/src/main/scala/org/apache/spark/SparkContext.scala ---
@@ -348,10 +348,24 @@ class SparkContext(config: SparkConf) extends Logging
with
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8730#issuecomment-139847346
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/8730#issuecomment-139847347
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/8730#issuecomment-139847334
[Test build #42378 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42378/console)
for PR 8730 at commit
Github user HyukjinKwon commented on a diff in the pull request:
https://github.com/apache/spark/pull/8391#discussion_r39345352
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/datasources/jdbc/JDBCRDD.scala
---
@@ -275,6 +275,10 @@ private[sql] class JDBCRDD(
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8710#issuecomment-139848070
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 opened a pull request:
https://github.com/apache/spark/pull/8734
[SPARK-10524][ML] Use the soft prediction to order categories' bins
JIRA: https://issues.apache.org/jira/browse/SPARK-10524
Currently we use the hard prediction
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8730#issuecomment-139892244
[Test build #42381 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42381/consoleFull)
for PR 8730 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8710#issuecomment-139891837
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/8721#issuecomment-139891835
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/8730#issuecomment-139891836
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/8734#issuecomment-139891838
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/8734#issuecomment-139887804
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8710#issuecomment-139892400
[Test build #42379 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42379/consoleFull)
for PR 8710 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8721#issuecomment-139892408
[Test build #42380 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42380/consoleFull)
for PR 8721 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8734#issuecomment-139892475
[Test build #42382 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42382/consoleFull)
for PR 8734 at commit
GitHub user viirya opened a pull request:
https://github.com/apache/spark/pull/8735
[SPARK-10571][Core] Fix incorrect appId in Spark REST / JSON API
JIRA: https://issues.apache.org/jira/browse/SPARK-10571
The app id shown in Spark REST / JSON API is not correct. This patch
GitHub user srowen opened a pull request:
https://github.com/apache/spark/pull/8736
[SPARK-10576] [BUILD] Move .java files out of src/main/scala
Move .java files in `src/main/scala` to `src/main/java` root, except for
`package-info.java` (to stay next to package.scala)
You can
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8734#issuecomment-139896122
[Test build #42382 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42382/console)
for PR 8734 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8735#issuecomment-139897740
[Test build #42383 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42383/consoleFull)
for PR 8735 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8730#issuecomment-139908417
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/8730#issuecomment-139908403
[Test build #42381 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42381/console)
for PR 8730 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8730#issuecomment-139908416
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/8180#issuecomment-139918725
[Test build #42385 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42385/consoleFull)
for PR 8180 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8734#issuecomment-139896144
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/8734#issuecomment-139896145
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/8735#issuecomment-139912789
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/8735#issuecomment-139912725
[Test build #42383 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42383/console)
for PR 8735 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8735#issuecomment-139912790
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/8721#issuecomment-139909356
[Test build #42380 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42380/console)
for PR 8721 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8721#issuecomment-139909375
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/8721#issuecomment-139909376
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/8710#issuecomment-139910837
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/8710#issuecomment-139910836
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8710#issuecomment-139910807
[Test build #42379 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42379/console)
for PR 8710 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8736#issuecomment-139915940
[Test build #42384 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42384/consoleFull)
for PR 8736 at commit
Github user mateiz commented on a diff in the pull request:
https://github.com/apache/spark/pull/8180#discussion_r39352275
--- Diff: core/src/main/scala/org/apache/spark/scheduler/DAGScheduler.scala
---
@@ -720,31 +843,82 @@ class DAGScheduler(
try {
// New
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8180#issuecomment-139918530
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 mateiz commented on the pull request:
https://github.com/apache/spark/pull/8180#issuecomment-139918503
Thanks for the comments; I've made the fixes. Let me know if anyone else
has other comments.
---
If your project is set up for it, you can reply to this email and have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8180#issuecomment-139918524
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/8735#issuecomment-139896948
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/8735#issuecomment-139896943
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/8736#issuecomment-139915363
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/8736#issuecomment-139915354
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7118#issuecomment-139933768
[Test build #42387 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42387/consoleFull)
for PR 7118 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8569#issuecomment-139938713
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/8569#issuecomment-139938712
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 viirya commented on the pull request:
https://github.com/apache/spark/pull/8735#issuecomment-139945955
@JoshRosen OK. Looks like this patch now only solves part of the problem.
Would you like to point out where it is the URL parameters which mixes these
up? I can find
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8564#issuecomment-139945848
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/8564#issuecomment-139945841
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/8214#issuecomment-139946556
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/8214#issuecomment-139946568
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/8561#issuecomment-139946567
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/8561#issuecomment-139946553
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8564#issuecomment-139946260
[Test build #42391 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42391/consoleFull)
for PR 8564 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8561#issuecomment-139946837
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/8561#issuecomment-139946836
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/8561#issuecomment-139946832
[Test build #42392 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42392/console)
for PR 8561 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8561#issuecomment-139946793
[Test build #42392 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42392/consoleFull)
for PR 8561 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7118#issuecomment-139947064
[Test build #42387 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42387/console)
for PR 7118 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8615#issuecomment-139947969
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/8737#issuecomment-139947899
[Test build #42394 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42394/consoleFull)
for PR 8737 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8615#issuecomment-139947945
[Test build #42386 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42386/console)
for PR 8615 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8737#issuecomment-139948049
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/8615#issuecomment-139947970
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/8615#issuecomment-139930935
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/8615#issuecomment-139930925
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/8569#issuecomment-139934680
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/8569#issuecomment-139934674
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8569#issuecomment-139938669
[Test build #42389 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42389/console)
for PR 8569 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8615#issuecomment-139947666
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/8615#issuecomment-139947675
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/8737#issuecomment-139948047
[Test build #42394 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42394/console)
for PR 8737 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8737#issuecomment-139948050
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/8736#issuecomment-139927643
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/7118#issuecomment-139933445
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/7118#issuecomment-139933440
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 KaiXinXiaoLei opened a pull request:
https://github.com/apache/spark/pull/8737
[SPARK-10582] using dynamic-executor-allocation, if a new AM restarts,
executors should be registered.
You can merge this pull request into a Git repository by running:
$ git pull
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7118#issuecomment-139947090
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/8214#issuecomment-139947114
[Test build #42393 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42393/consoleFull)
for PR 8214 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7118#issuecomment-139947091
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/8736#issuecomment-139927642
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/8736#issuecomment-139927630
[Test build #42384 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42384/console)
for PR 8736 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8615#issuecomment-139931178
[Test build #42386 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42386/consoleFull)
for PR 8615 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7118#issuecomment-139934570
[Test build #42388 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42388/consoleFull)
for PR 7118 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8552#issuecomment-139945419
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/8552#issuecomment-139945413
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 yanboliang commented on a diff in the pull request:
https://github.com/apache/spark/pull/8552#discussion_r39357714
--- Diff: mllib/src/main/scala/org/apache/spark/ml/tree/treeParams.scala ---
@@ -393,11 +383,18 @@ private[ml] trait GBTParams extends
TreeEnsembleParams
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/8735#issuecomment-139924416
I didn't highlight this super clearly in my JIRA report, but AFIAK the
scope of this issue also extends to the URL parameters also mixing these up.
We'll have to add
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8180#issuecomment-139929511
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
1 - 100 of 181 matches
Mail list logo
