Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10428#issuecomment-196676937
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/10428#issuecomment-196676941
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/10428#issuecomment-196676928
**[Test build #53165 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/53165/consoleFull)**
for PR 10428 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11714#issuecomment-196676820
**[Test build #53166 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/53166/consoleFull)**
for PR 11714 at commit
GitHub user gatorsmile opened a pull request:
https://github.com/apache/spark/pull/11714
[SPARK-13891] [SQL] [TEST] Issue Exceptions when Hitting the Max Iteration
Limit in Optimizer and Analyzer
What changes were proposed in this pull request?
This PR is to issue an
Github user retronym commented on the pull request:
https://github.com/apache/spark/pull/11410#issuecomment-196676313
Since offering review, I've found a more direct way to get to the object.
```
Welcome to Scala 2.11.8 (Java HotSpot(TM) 64-Bit Server VM, Java 1.8.0_71).
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10428#issuecomment-196676152
**[Test build #53165 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/53165/consoleFull)**
for PR 10428 at commit
Github user yinxusen commented on the pull request:
https://github.com/apache/spark/pull/11683#issuecomment-196675963
I'll add follow-up JIRA for nested pipeline support.
---
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/11410#issuecomment-196675771
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user yinxusen commented on the pull request:
https://github.com/apache/spark/pull/11683#issuecomment-196675833
@jkbradley Ready for another look.
---
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/11410#issuecomment-196675770
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/11410#issuecomment-196675688
**[Test build #53157 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/53157/consoleFull)**
for PR 11410 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11707#issuecomment-196675600
**[Test build #53164 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/53164/consoleFull)**
for PR 11707 at commit
Github user GayathriMurali commented on the pull request:
https://github.com/apache/spark/pull/11707#issuecomment-196675209
@jkbradley Fixed all the minor issues and changed title. Will wait for the
tests to complete
---
If your project is set up for it, you can reply to this email
Github user MLnick commented on a diff in the pull request:
https://github.com/apache/spark/pull/9#discussion_r56117376
--- Diff: mllib/src/main/scala/org/apache/spark/ml/clustering/KMeans.scala
---
@@ -258,6 +290,27 @@ class KMeans @Since("1.5.0") (
@Since("1.5.0")
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11713#issuecomment-196672117
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/11713#issuecomment-196672116
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/11713#issuecomment-196672054
**[Test build #53162 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/53162/consoleFull)**
for PR 11713 at commit
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/11664
---
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/11544#issuecomment-196671690
**[Test build #53163 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/53163/consoleFull)**
for PR 11544 at commit
Github user jkbradley commented on the pull request:
https://github.com/apache/spark/pull/11582#issuecomment-196671658
It looks like [https://github.com/apache/spark/pull/11707] is closer to
being merged now, so let's go with it instead. @wangmiao1981 Could you please
close this PR?
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/11664#issuecomment-196671610
Merging in master.
---
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/11664#issuecomment-196671197
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/11664#issuecomment-196671202
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11664#issuecomment-196670729
**[Test build #53156 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/53156/consoleFull)**
for PR 11664 at commit
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/11666
---
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/11666#issuecomment-196669270
Merging in 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 have
Github user jkbradley commented on a diff in the pull request:
https://github.com/apache/spark/pull/11582#discussion_r56116371
--- Diff: sql/hive/pom.xml ---
@@ -38,6 +38,11 @@
+org.scala-lang
--- End diff --
Please revert the change
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11683#issuecomment-196668764
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11683#issuecomment-196668475
**[Test build #53159 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/53159/consoleFull)**
for PR 11683 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11683#issuecomment-196668758
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 jkbradley commented on the pull request:
https://github.com/apache/spark/pull/11582#issuecomment-196668602
Also, to "fix the title," you'll need to put square brackets around the
JIRA: "[SPARK-13034]" and probably remove the colon ":"
---
If your project is set up for
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11666#issuecomment-196668356
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/11666#issuecomment-196668352
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 jkbradley commented on the pull request:
https://github.com/apache/spark/pull/11582#issuecomment-196668151
Thanks both for collaborating!
@wangmiao1981 If you want to get rid of the commits merged from master,
then you can do ```git rebase upstream/master```.
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11666#issuecomment-196667755
**[Test build #53155 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/53155/consoleFull)**
for PR 11666 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11711#issuecomment-196667168
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/11711#issuecomment-196667175
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11711#issuecomment-19828
**[Test build #53160 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/53160/consoleFull)**
for PR 11711 at commit
Github user HuJiayin commented on the pull request:
https://github.com/apache/spark/pull/9794#issuecomment-19064
ok!!
---
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11452#issuecomment-196665462
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/11452#issuecomment-196665465
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11713#issuecomment-196665456
**[Test build #53162 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/53162/consoleFull)**
for PR 11713 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11452#issuecomment-196665343
**[Test build #53153 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/53153/consoleFull)**
for PR 11452 at commit
Github user jkbradley commented on the pull request:
https://github.com/apache/spark/pull/9794#issuecomment-196665339
Very cool, thanks! I'll check it out.
---
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 carsonwang opened a pull request:
https://github.com/apache/spark/pull/11713
[SPARK-13889][YARN] Fix integer overflow when calculating the max number of
executor failure
## What changes were proposed in this pull request?
The max number of executor failure before
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11712#issuecomment-196664932
**[Test build #53161 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/53161/consoleFull)**
for PR 11712 at commit
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/11712#issuecomment-196664585
This is based on https://github.com/apache/spark/pull/11710
For the actual diff, just look at the last commit.
---
If your project is set up for it, you can
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/11712#issuecomment-196664605
cc @cloud-fan
---
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 rxin opened a pull request:
https://github.com/apache/spark/pull/11712
[SPARK-13890][SQL] Remove some internal classes' dependency on SQLContext
## What changes were proposed in this pull request?
In general it is better for internal classes to not depend on the
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11711#issuecomment-196664179
**[Test build #53160 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/53160/consoleFull)**
for PR 11711 at commit
Github user jkbradley commented on the pull request:
https://github.com/apache/spark/pull/10242#issuecomment-196663574
Great, 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 have this
Github user jkbradley commented on a diff in the pull request:
https://github.com/apache/spark/pull/9#discussion_r56115607
--- Diff: mllib/src/main/scala/org/apache/spark/ml/clustering/KMeans.scala
---
@@ -258,6 +290,27 @@ class KMeans @Since("1.5.0") (
@Since("1.5.0")
GitHub user zsxwing opened a pull request:
https://github.com/apache/spark/pull/11711
[SPARK-13888][DOC]Remove Akka Receiver doc and refer to the DStream Akka
project
## What changes were proposed in this pull request?
I have copied the docs of Streaming Akka to
Github user dbtsai commented on the pull request:
https://github.com/apache/spark/pull/11610#issuecomment-196662210
I will vote for approach 1.
SVD will be the most stable algorithm, but slowest O(mn^2 + n^3) compared
with Cholesky O(mn^2) or QR O(mn^2 - n^3/3) decomposition.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11297#issuecomment-196660958
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/11297#issuecomment-196660960
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11297#issuecomment-196660444
**[Test build #53154 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/53154/consoleFull)**
for PR 11297 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11701#issuecomment-196653856
**[Test build #53158 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/53158/consoleFull)**
for PR 11701 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11683#issuecomment-196653853
**[Test build #53159 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/53159/consoleFull)**
for PR 11683 at commit
Github user yinxusen commented on the pull request:
https://github.com/apache/spark/pull/11683#issuecomment-196653600
test it please
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11710#issuecomment-196649129
**[Test build #2641 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/2641/consoleFull)**
for PR 11710 at commit
Github user holdenk commented on the pull request:
https://github.com/apache/spark/pull/11109#issuecomment-196646711
Cool, I'll do a follow up PR and ping you on 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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11701#issuecomment-196645924
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/11701#issuecomment-196645925
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/11701#issuecomment-196645830
**[Test build #53148 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/53148/consoleFull)**
for PR 11701 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11410#issuecomment-196642687
**[Test build #53157 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/53157/consoleFull)**
for PR 11410 at commit
Github user cloud-fan commented on the pull request:
https://github.com/apache/spark/pull/11410#issuecomment-196642468
retest this please
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11664#issuecomment-196642073
**[Test build #53156 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/53156/consoleFull)**
for PR 11664 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11666#issuecomment-196641503
**[Test build #53155 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/53155/consoleFull)**
for PR 11666 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11645#issuecomment-196637005
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/11645#issuecomment-196637004
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/11645#issuecomment-196636867
**[Test build #53147 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/53147/consoleFull)**
for PR 11645 at commit
Github user yinxusen commented on the pull request:
https://github.com/apache/spark/pull/9#issuecomment-196636602
@jkbradley Sure. I'll check them later.
---
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 yinxusen commented on a diff in the pull request:
https://github.com/apache/spark/pull/9#discussion_r56110893
--- Diff: mllib/src/main/scala/org/apache/spark/ml/clustering/KMeans.scala
---
@@ -258,6 +290,27 @@ class KMeans @Since("1.5.0") (
@Since("1.5.0")
Github user jkbradley commented on the pull request:
https://github.com/apache/spark/pull/9#issuecomment-196635713
I'm also a fan of overriding other Params, but am Ok with it being in
another JIRA & PR.
---
If your project is set up for it, you can reply to this email and have
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11297#issuecomment-196635689
**[Test build #53154 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/53154/consoleFull)**
for PR 11297 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11690#issuecomment-196635276
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user jkbradley commented on a diff in the pull request:
https://github.com/apache/spark/pull/9#discussion_r56110707
--- Diff:
mllib/src/test/scala/org/apache/spark/ml/clustering/KMeansSuite.scala ---
@@ -108,6 +111,21 @@ class KMeansSuite extends SparkFunSuite with
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11690#issuecomment-196635271
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 jkbradley commented on a diff in the pull request:
https://github.com/apache/spark/pull/9#discussion_r56110698
--- Diff: mllib/src/main/scala/org/apache/spark/ml/clustering/KMeans.scala
---
@@ -269,6 +322,13 @@ class KMeans @Since("1.5.0") (
Github user jkbradley commented on a diff in the pull request:
https://github.com/apache/spark/pull/9#discussion_r56110689
--- Diff: mllib/src/main/scala/org/apache/spark/ml/clustering/KMeans.scala
---
@@ -196,6 +220,14 @@ object KMeansModel extends MLReadable[KMeansModel] {
Github user jkbradley commented on a diff in the pull request:
https://github.com/apache/spark/pull/9#discussion_r56110693
--- Diff: mllib/src/main/scala/org/apache/spark/ml/clustering/KMeans.scala
---
@@ -258,6 +290,27 @@ class KMeans @Since("1.5.0") (
@Since("1.5.0")
Github user jkbradley commented on a diff in the pull request:
https://github.com/apache/spark/pull/9#discussion_r56110686
--- Diff: mllib/src/main/scala/org/apache/spark/ml/clustering/KMeans.scala
---
@@ -169,12 +181,23 @@ object KMeansModel extends MLReadable[KMeansModel] {
Github user jkbradley commented on a diff in the pull request:
https://github.com/apache/spark/pull/9#discussion_r56110697
--- Diff: mllib/src/main/scala/org/apache/spark/ml/clustering/KMeans.scala
---
@@ -269,6 +322,13 @@ class KMeans @Since("1.5.0") (
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11690#issuecomment-196635042
**[Test build #53152 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/53152/consoleFull)**
for PR 11690 at commit
Github user cloud-fan commented on the pull request:
https://github.com/apache/spark/pull/11710#issuecomment-196632756
LGTM overall
---
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/11452#issuecomment-196630430
**[Test build #53153 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/53153/consoleFull)**
for PR 11452 at commit
Github user jkbradley commented on the pull request:
https://github.com/apache/spark/pull/8972#issuecomment-196630401
@jayantshekhar It looks like this PR is stale and now superceded by
[https://github.com/apache/spark/pull/9]. Could you please close this PR
and, if you have
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11690#issuecomment-196629830
**[Test build #53152 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/53152/consoleFull)**
for PR 11690 at commit
Github user jerryshao commented on the pull request:
https://github.com/apache/spark/pull/11690#issuecomment-196629407
Jenkins, retest this please.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11710#issuecomment-196629217
**[Test build #53151 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/53151/consoleFull)**
for PR 11710 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11710#issuecomment-196629220
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/11710#issuecomment-196629221
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/11682#issuecomment-196628698
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/11682#issuecomment-196628692
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/11710#issuecomment-196627309
**[Test build #53151 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/53151/consoleFull)**
for PR 11710 at commit
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/11710#discussion_r56109018
--- Diff:
sql/hive/src/main/scala/org/apache/spark/sql/hive/execution/DescribeHiveTableCommand.scala
---
@@ -31,33 +33,44 @@ import
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11682#issuecomment-196627725
**[Test build #53144 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/53144/consoleFull)**
for PR 11682 at commit
Github user shaneknapp commented on the pull request:
https://github.com/apache/spark/pull/11652#issuecomment-196627128
hi!
i'll circle up w/shiv tomorrow and get this sorted. :)
---
If your project is set up for it, you can reply to this email and have your
reply appear on
1 - 100 of 883 matches
Mail list logo
