Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9893#issuecomment-208639684
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/9893#issuecomment-208639687
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/5
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9893#issuecomment-208639207
**[Test build #55542 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/55542/consoleFull)**
for PR 9893 at commit
[`31e1d8b`](https://git
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12285#issuecomment-208638656
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12285#issuecomment-208638649
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 projec
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12285#issuecomment-208638218
**[Test build #55544 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/55544/consoleFull)**
for PR 12285 at commit
[`707c9bc`](https://g
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12313#issuecomment-208638398
**[Test build #8 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/8/consoleFull)**
for PR 12313 at commit
[`c4c6820`](https://gi
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11947#issuecomment-208638423
**[Test build #9 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/9/consoleFull)**
for PR 11947 at commit
[`161a3eb`](https://gi
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12310#issuecomment-208637636
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 projec
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12310#issuecomment-208637609
**[Test build #6 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/6/consoleFull)**
for PR 12310 at commit
[`ca8de82`](https://g
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12310#issuecomment-208637637
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
GitHub user rdblue opened a pull request:
https://github.com/apache/spark/pull/12313
[SPARK-14543] [SQL] Fix InsertIntoTable column resolution. (WIP)
WIP: this depends on #12239 and includes its commits for SPARK-14459.
## What changes are proposed in this pull request?
Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/12153#discussion_r59303595
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/datasources/FileScanRDD.scala
---
@@ -86,4 +87,20 @@ class FileScanRDD(
}
Github user zsxwing commented on a diff in the pull request:
https://github.com/apache/spark/pull/12247#discussion_r59303566
--- Diff:
sql/core/src/test/scala/org/apache/spark/sql/streaming/FileStreamSourceSuite.scala
---
@@ -341,6 +347,33 @@ class FileStreamSourceSuite extends
F
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12149#issuecomment-208635795
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 projec
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12149#issuecomment-208635798
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
Github user yanboliang commented on the pull request:
https://github.com/apache/spark/pull/12294#issuecomment-208635617
@mengxr We already have
[SPARK-13925](https://issues.apache.org/jira/browse/SPARK-13925) for add
summary statistics for SparkR glm. I will send a PR after this get
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12149#issuecomment-208635169
**[Test build #55546 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/55546/consoleFull)**
for PR 12149 at commit
[`a122143`](https://g
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12271#issuecomment-208634664
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 projec
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12271#issuecomment-208634671
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12271#issuecomment-208634574
**[Test build #2 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/2/consoleFull)**
for PR 12271 at commit
[`2e95ecf`](https://g
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12312#issuecomment-208632627
**[Test build #5 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/5/consoleFull)**
for PR 12312 at commit
[`8d496f6`](https://gi
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12310#issuecomment-208632622
**[Test build #6 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/6/consoleFull)**
for PR 12310 at commit
[`ca8de82`](https://gi
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12294#issuecomment-208632575
**[Test build #7 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/7/consoleFull)**
for PR 12294 at commit
[`9060397`](https://gi
GitHub user dongjoon-hyun opened a pull request:
https://github.com/apache/spark/pull/12312
[SPARK-14545][SQL] Improve `LikeSimplification` by adding `a%b` rule
## What changes were proposed in this pull request?
Current `LikeSimplification` handles the following four rules.
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/12310#issuecomment-208630342
```
java.lang.RuntimeException: Could not resolve previous ABI:
org.apache.spark:spark-graphx_2.11:1.6.0
at scala.sys.package$.error(package.scala:27)
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12310#issuecomment-208626048
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
Github user zsxwing commented on the pull request:
https://github.com/apache/spark/pull/12311#issuecomment-208625971
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12310#issuecomment-208626046
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 projec
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12310#issuecomment-208626006
**[Test build #55549 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/55549/consoleFull)**
for PR 12310 at commit
[`923a6e1`](https://g
Github user zsxwing commented on a diff in the pull request:
https://github.com/apache/spark/pull/12311#discussion_r59301687
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/ui/AllExecutionsPage.scala
---
@@ -55,6 +55,12 @@ private[ui] class AllExecutionsPage(paren
Github user yhuai commented on the pull request:
https://github.com/apache/spark/pull/12260#issuecomment-208625781
@davies Can you also review this? 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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12300#issuecomment-208625180
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 projec
Github user yhuai commented on the pull request:
https://github.com/apache/spark/pull/12067#issuecomment-208625402
@davies Can you review?
---
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/12300#issuecomment-208625182
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
Github user davies commented on a diff in the pull request:
https://github.com/apache/spark/pull/12311#discussion_r59301336
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/ui/AllExecutionsPage.scala
---
@@ -55,6 +55,12 @@ private[ui] class AllExecutionsPage(parent
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12300#issuecomment-208625178
**[Test build #1 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/1/consoleFull)**
for PR 12300 at commit
[`35682a8`](https://g
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12307#issuecomment-208624700
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12307#issuecomment-208624699
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 projec
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12307#issuecomment-208624594
**[Test build #55540 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/55540/consoleFull)**
for PR 12307 at commit
[`a7e0ab4`](https://g
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12271#issuecomment-208623925
**[Test build #2 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/2/consoleFull)**
for PR 12271 at commit
[`2e95ecf`](https://gi
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12311#issuecomment-208623937
**[Test build #0 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/0/consoleFull)**
for PR 12311 at commit
[`b25701f`](https://gi
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12246#issuecomment-208623948
**[Test build #3 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/3/consoleFull)**
for PR 12246 at commit
[`cc7baab`](https://gi
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12081#issuecomment-208623930
**[Test build #4 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/4/consoleFull)**
for PR 12081 at commit
[`38130a8`](https://gi
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12300#issuecomment-208623928
**[Test build #1 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/1/consoleFull)**
for PR 12300 at commit
[`35682a8`](https://gi
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/12311#issuecomment-208622959
Looks good!
---
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 andrewor14 commented on a diff in the pull request:
https://github.com/apache/spark/pull/12311#discussion_r59300812
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/ui/AllExecutionsPage.scala
---
@@ -55,6 +55,12 @@ private[ui] class AllExecutionsPage(pa
Github user shaneknapp commented on the pull request:
https://github.com/apache/spark/pull/9893#issuecomment-208622070
sounds good. i'm meeting w/the mesosphere guys thursday and this is a
topic i'm planning on bringing up.
On Mon, Apr 11, 2016 at 4:41 PM, Josh Rosen
Github user andrewor14 commented on a diff in the pull request:
https://github.com/apache/spark/pull/12271#discussion_r59300573
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/command/tables.scala ---
@@ -0,0 +1,80 @@
+/*
+ * Licensed to the Apache Software
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/9893
---
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 davies commented on the pull request:
https://github.com/apache/spark/pull/12311#issuecomment-208621490
cc @zsxwing
---
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
e
GitHub user davies opened a pull request:
https://github.com/apache/spark/pull/12311
[SPARK-14544] [SQL] improve performance of SQL UI tab
## What changes were proposed in this pull request?
This PR improve the performance of SQL UI by:
1) remove the details column
Github user andrewor14 commented on a diff in the pull request:
https://github.com/apache/spark/pull/12271#discussion_r59300596
--- Diff:
sql/hive/src/main/scala/org/apache/spark/sql/hive/execution/HiveSqlParser.scala
---
@@ -134,82 +136,117 @@ class HiveSqlAstBuilder extends Spar
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12310#issuecomment-208621180
**[Test build #55549 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/55549/consoleFull)**
for PR 12310 at commit
[`923a6e1`](https://gi
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/12270#issuecomment-208621507
I just merged #9893 so this should be ready for a rebase.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as we
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/9893#issuecomment-208620035
Looks like this compiled and fetched dependencies properly, so I'm going to
merge to master. Let's remember to re-enable these tests once we upgrade
Jenkins' kernel.
GitHub user JoshRosen opened a pull request:
https://github.com/apache/spark/pull/12310
[SPARK-14401][SPARK-1844] Use stock sbt-pom-reader and Maven-style dep
resolution
This patch modifies our SBT build to use a stock version of the
`sbt-pom-reader` plugin, rather than our own cus
Github user BryanCutler commented on a diff in the pull request:
https://github.com/apache/spark/pull/12079#discussion_r59299261
--- Diff: python/pyspark/mllib/feature.py ---
@@ -379,6 +379,17 @@ class HashingTF(object):
"""
def __init__(self, numFeatures=1 << 20):
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12247#issuecomment-208616091
**[Test build #55548 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/55548/consoleFull)**
for PR 12247 at commit
[`4cb1608`](https://gi
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12246#issuecomment-208612551
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12246#issuecomment-208612546
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 projec
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12246#issuecomment-208612531
**[Test build #55547 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/55547/consoleFull)**
for PR 12246 at commit
[`cbcb69d`](https://g
Github user jkbradley commented on the pull request:
https://github.com/apache/spark/pull/12089#issuecomment-208612860
Weird the merge_spark_pr script merged the wrong PR. Reverting...
---
If your project is set up for it, you can reply to this email and have your
reply appear on Git
Github user jkbradley commented on the pull request:
https://github.com/apache/spark/pull/12089#issuecomment-208611907
Backported to 1.6 and 1.5 as well now
---
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 davies commented on the pull request:
https://github.com/apache/spark/pull/12038#issuecomment-208610983
Yes
---
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/12246#issuecomment-208610845
**[Test build #55547 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/55547/consoleFull)**
for PR 12246 at commit
[`cbcb69d`](https://gi
Github user BryanCutler commented on the pull request:
https://github.com/apache/spark/pull/12308#issuecomment-208610202
> Since we seem to be adding the same param to multiple models, would it
maybe make sense to make this a shared param?
Maybe, I'm not sure if there are othe
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12247#issuecomment-208607923
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12247#issuecomment-208607918
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 projec
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12247#issuecomment-208607307
**[Test build #55539 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/55539/consoleFull)**
for PR 12247 at commit
[`a761692`](https://g
Github user zsxwing commented on a diff in the pull request:
https://github.com/apache/spark/pull/12247#discussion_r59297483
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/sources/interfaces.scala ---
@@ -129,8 +129,17 @@ trait SchemaRelationProvider {
* Implemented b
Github user marmbrus commented on a diff in the pull request:
https://github.com/apache/spark/pull/12247#discussion_r59297156
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/sources/interfaces.scala ---
@@ -129,8 +129,17 @@ trait SchemaRelationProvider {
* Implemented
Github user zzcclp commented on the pull request:
https://github.com/apache/spark/pull/12038#issuecomment-208604888
@davies has this pr cherry-picked into branch-1.6?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If you
Github user zsxwing commented on a diff in the pull request:
https://github.com/apache/spark/pull/12247#discussion_r59296806
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/sources/interfaces.scala ---
@@ -129,8 +129,17 @@ trait SchemaRelationProvider {
* Implemented b
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12309#issuecomment-208603933
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 p
GitHub user sitalkedia opened a pull request:
https://github.com/apache/spark/pull/12309
[SPARK-14542][CORE] PipeRDD should allow configurable buffer size forâ¦
## What changes were proposed in this pull request?
Currently PipedRDD internally uses PrintWriter to write data
Github user jaceklaskowski commented on a diff in the pull request:
https://github.com/apache/spark/pull/12119#discussion_r59296064
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/DataFrameWriter.scala ---
@@ -275,23 +277,64 @@ final class DataFrameWriter private[sql](df:
D
Github user marmbrus commented on a diff in the pull request:
https://github.com/apache/spark/pull/12247#discussion_r59295994
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/sources/interfaces.scala ---
@@ -129,8 +129,17 @@ trait SchemaRelationProvider {
* Implemented
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12285#issuecomment-208594887
**[Test build #55544 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/55544/consoleFull)**
for PR 12285 at commit
[`707c9bc`](https://gi
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12248#issuecomment-208594890
**[Test build #55545 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/55545/consoleFull)**
for PR 12248 at commit
[`0e46c58`](https://gi
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12149#issuecomment-208594889
**[Test build #55546 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/55546/consoleFull)**
for PR 12149 at commit
[`a122143`](https://gi
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12306#issuecomment-208594859
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 projec
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12306#issuecomment-208594869
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12306#issuecomment-208594618
**[Test build #55538 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/55538/consoleFull)**
for PR 12306 at commit
[`082bb86`](https://g
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/12248#issuecomment-208594533
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 JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/12248#issuecomment-208594528
It seems like we agree that this API is easy-to-support in Spark and
hard/impossible to implement as cleanly in client code. As a result, I think
this is okay to merg
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/12285#issuecomment-208594142
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
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/12301#issuecomment-208594045
Looks good.
---
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 andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/12303#issuecomment-208593831
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
enabl
Github user andrewor14 commented on a diff in the pull request:
https://github.com/apache/spark/pull/12303#discussion_r59293221
--- Diff:
sql/hive/src/main/scala/org/apache/spark/sql/hive/HiveStrategies.scala ---
@@ -23,9 +23,8 @@ import org.apache.spark.sql.catalyst.planning._
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12247#issuecomment-208593200
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12247#issuecomment-208593199
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 projec
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12149#issuecomment-208593074
**[Test build #55543 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/55543/consoleFull)**
for PR 12149 at commit
[`f66f0e9`](https://g
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12149#issuecomment-208593086
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12149#issuecomment-208593083
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 projec
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12247#issuecomment-208592951
**[Test build #55537 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/55537/consoleFull)**
for PR 12247 at commit
[`7a818a9`](https://g
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12308#issuecomment-208592757
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12308#issuecomment-208592752
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 projec
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12149#issuecomment-208592736
**[Test build #55543 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/55543/consoleFull)**
for PR 12149 at commit
[`f66f0e9`](https://gi
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12308#issuecomment-208592647
**[Test build #55541 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/55541/consoleFull)**
for PR 12308 at commit
[`7d362ed`](https://g
301 - 400 of 702 matches
Mail list logo
