Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/8881#issuecomment-143656104
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 an
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8910#issuecomment-143656095
[Test build #43056 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43056/consoleFull)
for PR 8910 at commit
[`0e54fb1`](https://gith
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 Gi
Github user yanboliang commented on a diff in the pull request:
https://github.com/apache/spark/pull/8884#discussion_r40528438
--- Diff:
mllib/src/main/scala/org/apache/spark/ml/regression/LinearRegression.scala ---
@@ -169,6 +181,33 @@ class LinearRegression(override val uid: Stri
Github user yanboliang commented on a diff in the pull request:
https://github.com/apache/spark/pull/8884#discussion_r40528592
--- Diff:
mllib/src/main/scala/org/apache/spark/ml/regression/LinearRegression.scala ---
@@ -169,6 +181,33 @@ class LinearRegression(override val uid: Stri
Github user Lewuathe commented on a diff in the pull request:
https://github.com/apache/spark/pull/8884#discussion_r40528709
--- Diff:
mllib/src/main/scala/org/apache/spark/ml/regression/LinearRegression.scala ---
@@ -199,8 +238,8 @@ class LinearRegression(override val uid: String)
Github user yanboliang commented on a diff in the pull request:
https://github.com/apache/spark/pull/8884#discussion_r40529250
--- Diff:
mllib/src/main/scala/org/apache/spark/ml/param/shared/sharedParams.scala ---
@@ -357,4 +357,17 @@ private[ml] trait HasWeightCol extends Params {
Github user yanboliang commented on a diff in the pull request:
https://github.com/apache/spark/pull/8884#discussion_r40529712
--- Diff:
mllib/src/test/scala/org/apache/spark/ml/regression/LinearRegressionSuite.scala
---
@@ -150,14 +155,14 @@ class LinearRegressionSuite extends Sp
Github user Lewuathe commented on a diff in the pull request:
https://github.com/apache/spark/pull/8884#discussion_r40530056
--- Diff:
mllib/src/test/scala/org/apache/spark/ml/regression/LinearRegressionSuite.scala
---
@@ -150,14 +155,14 @@ class LinearRegressionSuite extends Spar
GitHub user dmartinpro opened a pull request:
https://github.com/apache/spark/pull/8928
Fix two mistakes in programming-guide page
seperate -> separate
sees -> see
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/dmartinpro/spa
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8928#issuecomment-143684037
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 pr
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/8928#issuecomment-143687267
Yes, trivial but fine.
---
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/8928#issuecomment-143687621
[Test build #1820 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/1820/consoleFull)
for PR 8928 at commit
[`74aafce`](https://git
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8928#issuecomment-143690082
[Test build #1820 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/1820/console)
for PR 8928 at commit
[`74aafce`](https://github
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8910#issuecomment-143691131
[Test build #43056 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43056/console)
for PR 8910 at commit
[`0e54fb1`](https://github.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8910#issuecomment-143691233
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 project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8910#issuecomment-143691235
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/8928
---
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 enab
GitHub user suyanNone reopened a pull request:
https://github.com/apache/spark/pull/8927
[SPARK-10796][CORE]Resubmit stage while lost task in Zombie TaskSets
We meet that problem in Spark 1.3.0, and I also check the latest Spark
code, and I think that problem still exist.
desc:
Github user suyanNone commented on the pull request:
https://github.com/apache/spark/pull/8927#issuecomment-143698080
Reproduce that, so re-open 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 your project does no
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8927#issuecomment-143698654
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 have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8927#issuecomment-143698641
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 h
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8927#issuecomment-143699213
[Test build #43057 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43057/consoleFull)
for PR 8927 at commit
[`301da0a`](https://gith
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8927#issuecomment-143699525
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8927#issuecomment-143699519
[Test build #43057 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43057/console)
for PR 8927 at commit
[`301da0a`](https://github.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8927#issuecomment-143699522
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 project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8549#issuecomment-143703351
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 h
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8549#issuecomment-143703374
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 have
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8549#issuecomment-143703816
[Test build #43058 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43058/consoleFull)
for PR 8549 at commit
[`a9ef902`](https://gith
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8549#issuecomment-143714786
[Test build #43058 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43058/console)
for PR 8549 at commit
[`a9ef902`](https://github.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8549#issuecomment-143714866
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8549#issuecomment-143714864
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 project
Github user suyanNone commented on the pull request:
https://github.com/apache/spark/pull/8927#issuecomment-14378
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 hav
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8927#issuecomment-143722397
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 h
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8927#issuecomment-143722412
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 have
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8927#issuecomment-143723400
[Test build #43059 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43059/consoleFull)
for PR 8927 at commit
[`301da0a`](https://gith
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8927#issuecomment-143723906
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 project
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8927#issuecomment-143723901
[Test build #43059 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43059/console)
for PR 8927 at commit
[`301da0a`](https://github.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8927#issuecomment-143723907
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43
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 e
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8927#issuecomment-143732034
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 h
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8927#issuecomment-143732059
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 have
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8927#issuecomment-143734029
[Test build #43060 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43060/consoleFull)
for PR 8927 at commit
[`ce83c9b`](https://gith
Github user holdenk commented on the pull request:
https://github.com/apache/spark/pull/8214#issuecomment-143741114
ping? if its possible I'd like to get this merged in so I can fix the
template to be consistent.
---
If your project is set up for it, you can reply to this email and h
Github user vanzin commented on the pull request:
https://github.com/apache/spark/pull/8911#issuecomment-143744796
LGTM, merging to 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 not
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/8911
---
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 enab
Github user vanzin commented on the pull request:
https://github.com/apache/spark/pull/8910#issuecomment-143745833
LGTM, merging to master and branch-1.5.
---
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 do
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/8910
---
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 enab
Github user rama-mullapudi commented on the pull request:
https://github.com/apache/spark/pull/8374#issuecomment-143747859
Intent of the change is make field metadata available to getJDBCType so it
can be used by dialects to handle special cases. One I was trying to solve is
by defaul
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8922#issuecomment-143749165
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 h
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8922#issuecomment-143749198
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 have
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8922#issuecomment-143750658
[Test build #43061 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43061/consoleFull)
for PR 8922 at commit
[`f7a7b2d`](https://gith
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8775#issuecomment-143751514
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 h
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8775#issuecomment-143751538
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 have
Github user vanzin commented on the pull request:
https://github.com/apache/spark/pull/8775#issuecomment-143751385
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 feat
Github user vanzin commented on the pull request:
https://github.com/apache/spark/pull/8887#issuecomment-143751726
/cc @squito also
---
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 featur
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8374#issuecomment-143752657
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 h
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8374#issuecomment-143752683
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 have
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8374#issuecomment-143753230
[Test build #43063 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43063/consoleFull)
for PR 8374 at commit
[`5f532e8`](https://gith
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8775#issuecomment-143753555
[Test build #43062 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43062/consoleFull)
for PR 8775 at commit
[`f3bb7b4`](https://gith
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8374#issuecomment-143754448
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8374#issuecomment-143754446
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 project
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8374#issuecomment-143754440
[Test build #43063 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43063/console)
for PR 8374 at commit
[`5f532e8`](https://github.
Github user nilmeier commented on the pull request:
https://github.com/apache/spark/pull/8563#issuecomment-143771419
Thank you @frreiss for the review! I will address these issues and update
the pull request in the next few days. Cheers, J
---
If your project is set up for it, you
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8927#issuecomment-143774601
[Test build #43060 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43060/console)
for PR 8927 at commit
[`ce83c9b`](https://github.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8927#issuecomment-143774744
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 project
Github user pallavipr commented on the pull request:
https://github.com/apache/spark/pull/8374#issuecomment-143775002
Rama, while specifying DataFrame metadata length is good approach, can we
please have dbStringMappingType and dbStringMappingLength as properties on the
connection url
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8927#issuecomment-143774745
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43
Github user mengxr commented on the pull request:
https://github.com/apache/spark/pull/8926#issuecomment-143782550
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
enab
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8926#issuecomment-143783456
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 h
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8926#issuecomment-143783496
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 have
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8926#issuecomment-143784474
[Test build #43064 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43064/consoleFull)
for PR 8926 at commit
[`fa611d9`](https://gith
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8926#issuecomment-143784661
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 project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8926#issuecomment-143784662
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8926#issuecomment-143784650
[Test build #43064 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43064/console)
for PR 8926 at commit
[`fa611d9`](https://github.
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8922#issuecomment-143785651
[Test build #43061 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43061/console)
for PR 8922 at commit
[`f7a7b2d`](https://github.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8922#issuecomment-143785810
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 project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8922#issuecomment-143785812
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43
Github user dbtsai commented on a diff in the pull request:
https://github.com/apache/spark/pull/8884#discussion_r40569761
--- Diff:
mllib/src/main/scala/org/apache/spark/ml/regression/LinearRegression.scala ---
@@ -199,8 +238,8 @@ class LinearRegression(override val uid: String)
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7052#issuecomment-143788957
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 h
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7052#issuecomment-143789009
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 have
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7052#issuecomment-143791386
[Test build #43065 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43065/consoleFull)
for PR 7052 at commit
[`80599a4`](https://gith
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7052#issuecomment-143792699
[Test build #43065 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43065/console)
for PR 7052 at commit
[`80599a4`](https://github.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7052#issuecomment-143792708
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7052#issuecomment-143792704
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 project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7052#issuecomment-143797924
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 h
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7052#issuecomment-143797943
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 have
Github user vanzin commented on the pull request:
https://github.com/apache/spark/pull/8753#issuecomment-143797926
@jaceklaskowski could you close this PR please? 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
Github user WangTaoTheTonic commented on the pull request:
https://github.com/apache/spark/pull/5722#issuecomment-143799075
I think we better keep backwards compatibility and treat [min, max] as a
fine grained control on exact port while the "only 8080" with max retries as a
coarse on
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7052#issuecomment-143799326
[Test build #43066 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43066/consoleFull)
for PR 7052 at commit
[`a7e4d17`](https://gith
Github user WangTaoTheTonic commented on the pull request:
https://github.com/apache/spark/pull/2994#issuecomment-143799798
Hi @harishreedharan, I think this is a nice feature which is very helpful
for user who tries to write DStream back into Kafka. The implement is very neat
too.
Github user vanzin commented on a diff in the pull request:
https://github.com/apache/spark/pull/7739#discussion_r40576075
--- Diff: bin/spark-shell ---
@@ -35,7 +35,8 @@ export _SPARK_CMD_USAGE="Usage: ./bin/spark-shell
[options]"
# so we need to add the "-Dscala.usejavacp=tr
Github user vanzin commented on a diff in the pull request:
https://github.com/apache/spark/pull/7739#discussion_r40576243
--- Diff: bin/spark-shell ---
@@ -35,7 +35,8 @@ export _SPARK_CMD_USAGE="Usage: ./bin/spark-shell
[options]"
# so we need to add the "-Dscala.usejavacp=tr
Github user vanzin commented on a diff in the pull request:
https://github.com/apache/spark/pull/7739#discussion_r40576297
--- Diff: core/src/main/scala/org/apache/spark/SparkConf.scala ---
@@ -465,6 +466,10 @@ class SparkConf(loadDefaults: Boolean) extends
Cloneable with Logging {
Github user vanzin commented on a diff in the pull request:
https://github.com/apache/spark/pull/7739#discussion_r40576432
--- Diff: core/src/main/scala/org/apache/spark/SparkConf.scala ---
@@ -505,6 +510,23 @@ class SparkConf(loadDefaults: Boolean) extends
Cloneable with Logging {
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8775#issuecomment-143804474
[Test build #43062 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43062/console)
for PR 8775 at commit
[`f3bb7b4`](https://github.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8775#issuecomment-143804641
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8775#issuecomment-143804636
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 project
Github user shivaram commented on the pull request:
https://github.com/apache/spark/pull/8920#issuecomment-143810231
Jenkins, 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 f
Github user shivaram commented on the pull request:
https://github.com/apache/spark/pull/8920#issuecomment-143810259
cc @sun-rui
---
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
1 - 100 of 302 matches
Mail list logo
