GitHub user liancheng opened a pull request:
https://github.com/apache/spark/pull/6520
[SPARK-7849] [SQL] [Docs] Updates SQL programming guide for 1.4
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/liancheng/spark spark-7849
Github user liancheng commented on the pull request:
https://github.com/apache/spark/pull/6520#issuecomment-107070166
@yhuai @rxin @marmbrus Please help review, 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 andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/6317#issuecomment-107072614
Sorry for the late response, lgtm too
---
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 MechCoder commented on a diff in the pull request:
https://github.com/apache/spark/pull/6112#discussion_r31383352
--- Diff: mllib/src/main/scala/org/apache/spark/mllib/linalg/Vectors.scala
---
@@ -717,6 +719,49 @@ class SparseVector(
new SparseVector(size,
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/6505#discussion_r31384479
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/analysis/HiveTypeCoercion.scala
---
@@ -482,30 +482,48 @@ trait HiveTypeCoercion {
}
Github user harishreedharan commented on the pull request:
https://github.com/apache/spark/pull/5792#issuecomment-107087219
Failed in sql/hive tests somewhere.
---
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 harishreedharan commented on the pull request:
https://github.com/apache/spark/pull/5792#issuecomment-107087226
Jenkins, test 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
Github user MechCoder commented on a diff in the pull request:
https://github.com/apache/spark/pull/6112#discussion_r31382216
--- Diff: mllib/src/main/scala/org/apache/spark/mllib/linalg/Vectors.scala
---
@@ -717,6 +719,49 @@ class SparseVector(
new SparseVector(size,
Github user MechCoder commented on a diff in the pull request:
https://github.com/apache/spark/pull/6112#discussion_r31382229
--- Diff: mllib/src/main/scala/org/apache/spark/mllib/linalg/Vectors.scala
---
@@ -717,6 +719,49 @@ class SparseVector(
new SparseVector(size,
Github user MechCoder commented on a diff in the pull request:
https://github.com/apache/spark/pull/6112#discussion_r31382319
--- Diff: mllib/src/main/scala/org/apache/spark/mllib/linalg/Vectors.scala
---
@@ -717,6 +719,49 @@ class SparseVector(
new SparseVector(size,
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6505#issuecomment-107065413
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/6519#issuecomment-107067208
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/6519#issuecomment-107067203
[Test build #33812 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/33812/consoleFull)
for PR 6519 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6521#issuecomment-107070571
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 rxin commented on the pull request:
https://github.com/apache/spark/pull/6515#issuecomment-107074328
Jenkins, retest this please.
On Saturday, May 30, 2015, Yijie Shen notificati...@github.com wrote:
How can I ask Jenkins to retest it?
â
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6319#issuecomment-107077847
[Test build #33816 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/33816/consoleFull)
for PR 6319 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/5701#issuecomment-107077868
[Test build #33817 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/33817/consoleFull)
for PR 5701 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/5701#issuecomment-107077870
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/6319#issuecomment-107077893
[Test build #33816 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/33816/consoleFull)
for PR 6319 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6319#issuecomment-107077894
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/5792#issuecomment-107078539
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/5792#issuecomment-107078529
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/5792#issuecomment-107085213
[Test build #33819 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/33819/consoleFull)
for PR 5792 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/5792#issuecomment-107085216
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 rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/6505#discussion_r31384407
--- Diff: sql/core/src/test/scala/org/apache/spark/sql/SQLQuerySuite.scala
---
@@ -1331,4 +1331,27 @@ class SQLQuerySuite extends QueryTest with
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/4685
---
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 rxin commented on the pull request:
https://github.com/apache/spark/pull/6520#issuecomment-107076765
I've merged this. I will fix problems when I go through the doc myself
later today.
---
If your project is set up for it, you can reply to this email and have your
reply
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/6520
---
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 rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/6505#discussion_r31384423
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/analysis/HiveTypeCoercion.scala
---
@@ -482,30 +482,48 @@ trait HiveTypeCoercion {
}
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6515#issuecomment-107085777
[Test build #33815 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/33815/consoleFull)
for PR 6515 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6515#issuecomment-107085786
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 rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/6505#discussion_r31384583
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/analysis/HiveTypeCoercion.scala
---
@@ -482,30 +482,48 @@ trait HiveTypeCoercion {
}
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6505#issuecomment-107060806
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 erfangc commented on the pull request:
https://github.com/apache/spark/pull/2765#issuecomment-107060825
This feature would definitely be helpful. Thanks to @wangxiaojing and
whoever continuing to work on PR!
---
If your project is set up for it, you can reply to this
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6505#issuecomment-107060800
[Test build #33810 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/33810/consoleFull)
for PR 6505 at commit
Github user GeorgeDittmar commented on a diff in the pull request:
https://github.com/apache/spark/pull/6112#discussion_r31382691
--- Diff: mllib/src/main/scala/org/apache/spark/mllib/linalg/Vectors.scala
---
@@ -717,6 +719,49 @@ class SparseVector(
new
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6520#issuecomment-107070475
[Test build #33813 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/33813/consoleFull)
for PR 6520 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6520#issuecomment-107070258
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 liancheng opened a pull request:
https://github.com/apache/spark/pull/6521
[SQL] [Minor] Fixes a minor comment mistake in IsolatedClientLoader
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/liancheng/spark
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/5792#issuecomment-107078552
[Test build #33818 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/33818/consoleFull)
for PR 5792 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6519#issuecomment-107064091
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/6519#issuecomment-107064065
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/6519#issuecomment-107064741
[Test build #33812 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/33812/consoleFull)
for PR 6519 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6521#issuecomment-107070576
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/6521#issuecomment-107070732
[Test build #33814 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/33814/consoleFull)
for PR 6521 at commit
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/6521#discussion_r31383045
--- Diff:
sql/hive/src/main/scala/org/apache/spark/sql/hive/client/IsolatedClientLoader.scala
---
@@ -90,14 +90,14 @@ private[hive] object
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6515#issuecomment-107077638
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/5701#issuecomment-107077629
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/6515#issuecomment-107077751
[Test build #33815 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/33815/consoleFull)
for PR 6515 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6319#issuecomment-107077625
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/5701#issuecomment-107077640
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/5701#issuecomment-107077689
[Test build #33817 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/33817/consoleFull)
for PR 5701 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6319#issuecomment-107077639
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/6515#issuecomment-107077624
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/6520#issuecomment-107078191
[Test build #33813 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/33813/consoleFull)
for PR 6520 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6520#issuecomment-107078211
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/5792#issuecomment-107078738
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/6521#issuecomment-107078758
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/5792#issuecomment-107078743
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 rxin commented on the pull request:
https://github.com/apache/spark/pull/6515#issuecomment-107087027
@yijieshen how do I run 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 not have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6505#issuecomment-107059226
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 GeorgeDittmar commented on a diff in the pull request:
https://github.com/apache/spark/pull/6112#discussion_r31382733
--- Diff: mllib/src/main/scala/org/apache/spark/mllib/linalg/Vectors.scala
---
@@ -717,6 +719,49 @@ class SparseVector(
new
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6520#issuecomment-107070253
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 rxin commented on the pull request:
https://github.com/apache/spark/pull/6515#issuecomment-107077167
Jenkins, retest this please.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/6319#issuecomment-107077226
Jenkins, test 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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/5792#issuecomment-107078769
[Test build #33819 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/33819/consoleFull)
for PR 5792 at commit
Github user yhuai commented on the pull request:
https://github.com/apache/spark/pull/6505#issuecomment-107087361
Can you give some examples to explain what is the problem?
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/5792#issuecomment-107087369
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/5792#issuecomment-107087375
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 yijieshen commented on the pull request:
https://github.com/apache/spark/pull/6515#issuecomment-106993985
Test more Error bug patterns manually, work as expected.
However, after an error report, if no `mvn clean` called before next `mvn
package`, and not changing the
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/6516#discussion_r31378408
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/analysis/HiveTypeCoercion.scala
---
@@ -511,32 +510,6 @@ trait HiveTypeCoercion {
}
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/6516#discussion_r31378410
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/analysis/HiveTypeCoercion.scala
---
@@ -511,32 +510,6 @@ trait HiveTypeCoercion {
}
Github user yijieshen commented on the pull request:
https://github.com/apache/spark/pull/6515#issuecomment-106994629
Not that sure how lint-java works. If I understand correctly, in lint-java,
we should run error prone separately like what lint-scala does?
If so, seems not
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/6505#issuecomment-106994617
cc @yhuai
---
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6405#issuecomment-106993379
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 rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/6405#discussion_r31378244
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/Expression.scala
---
@@ -86,12 +86,18 @@ abstract class Expression extends
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6405#issuecomment-106993862
[Test build #33797 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/33797/consoleFull)
for PR 6405 at commit
Github user cloud-fan commented on the pull request:
https://github.com/apache/spark/pull/6405#issuecomment-106994447
The tests will still fail as we need 2 more changes to satisfy the type
equal constraint for `EqualTo`.
* https://github.com/apache/spark/pull/6505 to avoid
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6405#issuecomment-106993384
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 tnachen closed the pull request at:
https://github.com/apache/spark/pull/6512
---
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/6405#issuecomment-106993495
[Test build #33798 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/33798/consoleFull)
for PR 6405 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6405#issuecomment-106993751
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/6517#issuecomment-106993746
[Test build #33800 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/33800/consoleFull)
for PR 6517 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6405#issuecomment-106993873
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/6405#issuecomment-106993749
[Test build #33799 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/33799/consoleFull)
for PR 6405 at commit
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/6502#issuecomment-106994572
@vanzin - thanks, this looks great.
Can you do 3 things?
1. Make the import ordering configurable.
2. The style rule is pretty complicated. Add some
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/6515#issuecomment-106994189
Got it - as long as it is fine on Jenkins, I think it is OK. We can rely on
Jenkins to do this anyway.
One thing to add is lint-java file in /dev folder.
---
If
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6405#issuecomment-106994236
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/6405#issuecomment-106994241
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 rxin commented on the pull request:
https://github.com/apache/spark/pull/6515#issuecomment-106994699
Ah ok. So the only way to run this is to use mvn compile?
---
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6405#issuecomment-106993697
[Test build #33799 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/33799/consoleFull)
for PR 6405 at commit
Github user tnachen commented on the pull request:
https://github.com/apache/spark/pull/6517#issuecomment-106993604
@andrewor14 PTAL, this is against master branch
---
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/6405#issuecomment-106993621
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/6517#issuecomment-106993629
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/6405#issuecomment-106993581
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/6517#issuecomment-106993620
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/6405#issuecomment-106993628
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 tnachen opened a pull request:
https://github.com/apache/spark/pull/6517
[SPARK-7962][MESOS] Fix master url parsing in rest submission client.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/tnachen/spark
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6405#issuecomment-106993580
[Test build #33798 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/33798/consoleFull)
for PR 6405 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6405#issuecomment-106994335
[Test build #33801 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/33801/consoleFull)
for PR 6405 at commit
1 - 100 of 401 matches
Mail list logo
