Github user yhuai commented on a diff in the pull request:
https://github.com/apache/spark/pull/8492#discussion_r38225619
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/collectionOperations.scala
---
@@ -145,46 +143,42 @@ case class ArrayContains(l
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8398#issuecomment-135841402
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8398#issuecomment-135841400
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8398#issuecomment-135841278
[Test build #41746 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41746/console)
for PR 8398 at commit
[`77869c9`](https://github.
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8493#issuecomment-135840520
[Test build #41752 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41752/consoleFull)
for PR 8493 at commit
[`a14dba5`](https://gith
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8493#issuecomment-135839282
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/8493#issuecomment-135839307
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/8493#issuecomment-135839041
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 zapletal-martin commented on the pull request:
https://github.com/apache/spark/pull/8377#issuecomment-135837710
@mengxr, I am planning to work on this in around 5 hours. Unfortunately I
won't be able to progress it before that.
---
If your project is set up for it, you ca
Github user feynmanliang commented on the pull request:
https://github.com/apache/spark/pull/8491#issuecomment-135836967
@mengxr WRT 1, completely agree and created SPARK-10333
WRT 2, I agree we should be consistent throughout the code examples.
However, I've felt awkward writ
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8492#issuecomment-135836177
[Test build #41751 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41751/consoleFull)
for PR 8492 at commit
[`6887185`](https://gith
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8492#issuecomment-135834195
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/8492#issuecomment-135834146
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/8509#issuecomment-135832176
[Test build #41750 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41750/consoleFull)
for PR 8509 at commit
[`88ab2a9`](https://gith
Github user liancheng commented on the pull request:
https://github.com/apache/spark/pull/8509#issuecomment-135831611
@rxin Considering this is a pretty major change and SPARK-10301 isn't a
blocker, I'm not quite sure whether we should include this into 1.5 at this
moment. Another thi
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8509#issuecomment-135830945
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/8509#issuecomment-135830917
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 yhuai commented on a diff in the pull request:
https://github.com/apache/spark/pull/8492#discussion_r38219598
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/collectionOperations.scala
---
@@ -145,46 +143,43 @@ case class ArrayContains(l
Github user mengxr commented on the pull request:
https://github.com/apache/spark/pull/8377#issuecomment-135828891
@zapletal-martin Do you have time to update this time? It would be nice to
merge this first before I make a pass to the whole user guide to avoid merge
conflicts. Or I ca
Github user liancheng commented on a diff in the pull request:
https://github.com/apache/spark/pull/8509#discussion_r38217769
--- Diff:
sql/core/src/test/scala/org/apache/spark/sql/test/SharedSQLContext.scala ---
@@ -17,7 +17,7 @@
package org.apache.spark.sql.test
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8503#issuecomment-135825325
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8503#issuecomment-135825324
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/8503#issuecomment-135825270
[Test build #41747 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41747/console)
for PR 8503 at commit
[`17472b9`](https://github.
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8509#issuecomment-135824724
[Test build #41749 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41749/consoleFull)
for PR 8509 at commit
[`a53cf34`](https://gith
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8509#issuecomment-135823896
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/8509#issuecomment-135823874
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 liancheng opened a pull request:
https://github.com/apache/spark/pull/8509
[SPARK-10301] [SQL] Fixes schema merging for nested structs
This PR can be quite challenging to review. I'm trying to give a detailed
description of the problem as well as its solution here.
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/8343
---
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 shivaram commented on the pull request:
https://github.com/apache/spark/pull/8503#issuecomment-135822495
cc @sun-rui , @yu-iskw (especially for the rdname changes)
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as wel
Github user shivaram commented on the pull request:
https://github.com/apache/spark/pull/8343#issuecomment-135821208
lint-r looks fine, Merging this.
---
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 n
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6297#issuecomment-135820655
[Test build #41748 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41748/consoleFull)
for PR 6297 at commit
[`0902ceb`](https://gith
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8503#issuecomment-135819125
[Test build #41747 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41747/consoleFull)
for PR 8503 at commit
[`17472b9`](https://gith
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/6599#issuecomment-135818982
Backported to 1.4.2.
---
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/6297#issuecomment-135817886
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/6297#issuecomment-135817978
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/8503#issuecomment-135814974
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/8503#issuecomment-135815023
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 shivaram commented on the pull request:
https://github.com/apache/spark/pull/8503#issuecomment-135814324
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 zsxwing commented on a diff in the pull request:
https://github.com/apache/spark/pull/8464#discussion_r38213328
--- Diff:
sql/core/src/test/scala/org/apache/spark/sql/execution/local/FilterNodeSuite.scala
---
@@ -0,0 +1,41 @@
+/*
+* Licensed to the Apache Softw
Github user mengxr commented on the pull request:
https://github.com/apache/spark/pull/8505#issuecomment-135802592
Looking at the changes, I wonder whether we need to annotate original
public methods/variables that have the same since version as the class. Java
doesn't do this
(http:
Github user mateiz commented on the pull request:
https://github.com/apache/spark/pull/7699#issuecomment-135802458
Regarding the "wider class of problems", I just meant that the core problem
here seems to be that tasks don't get identified correctly. This also seems to
affect other co
Github user lresende commented on the pull request:
https://github.com/apache/spark/pull/8393#issuecomment-135800505
Looks like there is a DB2 Express version that is free, let me see if I can
make a docker image with that.
---
If your project is set up for it, you can reply to this
Github user mengxr commented on a diff in the pull request:
https://github.com/apache/spark/pull/8505#discussion_r38209961
--- Diff: mllib/src/main/scala/org/apache/spark/ml/feature/Binarizer.scala
---
@@ -31,10 +31,12 @@ import org.apache.spark.sql.types.{DoubleType,
StructType}
Github user mengxr commented on the pull request:
https://github.com/apache/spark/pull/8507#issuecomment-135798779
Please see my comments on the JIRA page. This apparently complicates the
implementation. I think we need to understand the trade-offs more.
---
If your project is set up
Github user mengxr commented on the pull request:
https://github.com/apache/spark/pull/8487#issuecomment-135798504
LGTM except some minor issues with Java imports. I will fix those in a
separate PR. Merged into master and branch-1.5. Thanks!
---
If your project is set up for it, you
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/8487
---
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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/8502
---
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 squito commented on the pull request:
https://github.com/apache/spark/pull/8502#issuecomment-135789010
thanks @jerryshao , good catch! I suppose I never thought about it since
the unit test doesn't actually use the server, but the service will start it in
any case.
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8398#issuecomment-135787366
[Test build #41746 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41746/consoleFull)
for PR 8398 at commit
[`77869c9`](https://gith
Github user thegiive commented on the pull request:
https://github.com/apache/spark/pull/8129#issuecomment-135786660
hi @JoshRosen , @andrewor14 , @srowen
Viirya and I are in the same team. Currently Spark standalone has only one
FIFO scheduler outside the application and th
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8398#issuecomment-135785134
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/8398#issuecomment-135785107
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 tgravescs commented on the pull request:
https://github.com/apache/spark/pull/8398#issuecomment-135782690
@rxin @JoshRosen Since this is in core would one of you like to take a
look.
Minor nit in spacing otherwise LGTM.
---
If your project is set up for it, you
Github user tgravescs commented on a diff in the pull request:
https://github.com/apache/spark/pull/8398#discussion_r38202472
--- Diff: core/src/main/scala/org/apache/spark/SecurityManager.scala ---
@@ -321,7 +330,16 @@ private[spark] class SecurityManager(sparkConf:
SparkConf)
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8508#issuecomment-135778613
[Test build #41745 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41745/console)
for PR 8508 at commit
[`d44ac06`](https://github.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8508#issuecomment-135778749
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8508#issuecomment-135778748
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8508#issuecomment-135775547
[Test build #41745 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41745/consoleFull)
for PR 8508 at commit
[`d44ac06`](https://gith
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8508#issuecomment-135774512
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/8508#issuecomment-135774527
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/8508#issuecomment-135768864
[Test build #41744 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41744/console)
for PR 8508 at commit
[`730b0a7`](https://github.
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8508#issuecomment-135768784
[Test build #41744 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41744/consoleFull)
for PR 8508 at commit
[`730b0a7`](https://gith
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8508#issuecomment-135768868
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8508#issuecomment-135767707
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/8508#issuecomment-135767680
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 yanboliang opened a pull request:
https://github.com/apache/spark/pull/8508
[SPARK-10026] [ML] [PySpark] Implement some common Params for regression in
PySpark
Currently some Params are not common classes in Python API which lead we
need to write them for each class. Th
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8507#issuecomment-135755046
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 vinodkc opened a pull request:
https://github.com/apache/spark/pull/8507
[SPARK-10199][MLlib]Avoid using reflections for parquet model save
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/vinodkc/spark fix_SPARK-10200
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8502#issuecomment-135745782
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8502#issuecomment-135745780
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/8502#issuecomment-135745726
[Test build #41741 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41741/console)
for PR 8502 at commit
[`bcb93a8`](https://github.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8506#issuecomment-135745326
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 josiahsams opened a pull request:
https://github.com/apache/spark/pull/8506
[SPARK-10172][core]Fix for HistoryServer webUI mess up during sorting
This pull request is to address the JIRA SPARK-10172 (History Server web UI
gets messed up when sorting on any column).
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8493#issuecomment-135742768
[Test build #1702 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/1702/console)
for PR 8493 at commit
[`a14dba5`](https://github
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8498#issuecomment-135735975
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/8498#issuecomment-135735979
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8498#issuecomment-135735710
[Test build #41734 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41734/console)
for PR 8498 at commit
[`2790270`](https://github.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8500#issuecomment-135727710
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/8505#issuecomment-135727723
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8500#issuecomment-135727711
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41
GitHub user martinbrown opened a pull request:
https://github.com/apache/spark/pull/8505
[SPARK-10258] [DOCUMENTATION, ML] Adding Since() Annotations to ml/feature
Unsure what to do for SQLTransformer since it's in master but not in any
tagged release.
You can merge this pull requ
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8500#issuecomment-135727626
[Test build #41739 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41739/console)
for PR 8500 at commit
[`51ffea1`](https://github.
Github user frodeso commented on the pull request:
https://github.com/apache/spark/pull/8252#issuecomment-135723748
This backport also includes the refactor of TakeOrdered to
TakeOrderedAndProject, which breaks code that refers to TakeOrdered. In a minor
version update that is perhaps
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8499#issuecomment-135723505
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8499#issuecomment-135723410
[Test build #41738 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41738/console)
for PR 8499 at commit
[`28d213d`](https://github.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8499#issuecomment-135723504
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/8504#issuecomment-135723227
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/8504#issuecomment-135723230
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8504#issuecomment-135723220
[Test build #41743 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41743/console)
for PR 8504 at commit
[`95698eb`](https://github.
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8504#issuecomment-135722891
[Test build #41743 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41743/consoleFull)
for PR 8504 at commit
[`95698eb`](https://gith
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8484#issuecomment-135722716
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/8484#issuecomment-135722720
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8484#issuecomment-135722528
[Test build #41736 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41736/console)
for PR 8484 at commit
[`fe7b7bf`](https://github.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8504#issuecomment-135722057
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/8504#issuecomment-135722122
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 jerryshao opened a pull request:
https://github.com/apache/spark/pull/8504
[SPARK-10288][Yarn][WIP] Add REST client for Spark on Yarn to support
application submission
This PR adds a REST client for Spark on Yarn to submit, query and kill
applications. This function is
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8485#issuecomment-135718650
[Test build #41742 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41742/console)
for PR 8485 at commit
[`d5d5270`](https://github.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8485#issuecomment-135718766
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8485#issuecomment-135718765
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 felixcheung commented on the pull request:
https://github.com/apache/spark/pull/8503#issuecomment-135714911
@shivaram
---
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
301 - 400 of 489 matches
Mail list logo
