Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10751#issuecomment-171535476
**[Test build #49376 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49376/consoleFull)**
for PR 10751 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10751#issuecomment-171535628
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/10749#issuecomment-171539349
**[Test build #2380 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/2380/consoleFull)**
for PR 10749 at commit
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/10737#discussion_r49690466
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/conditionalExpressions.scala
---
@@ -137,45 +137,65 @@ case class
GitHub user rxin opened a pull request:
https://github.com/apache/spark/pull/10755
[SPARK-12771][SQL] Improve CaseWhen codegen by removing "got" variable
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/rxin/spark SPARK-12771
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10755#issuecomment-171548270
**[Test build #49385 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49385/consoleFull)**
for PR 10755 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10753#issuecomment-171556796
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/10753#issuecomment-171556795
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/10753#issuecomment-171558534
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/10753#issuecomment-171558536
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/10753#issuecomment-171558386
**[Test build #49381 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49381/consoleFull)**
for PR 10753 at commit
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/10658#discussion_r49688028
--- Diff:
launcher/src/main/java/org/apache/spark/launcher/SparkSubmitCommandBuilder.java
---
@@ -258,9 +256,10 @@
private List
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10751#issuecomment-171533138
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/10731#issuecomment-171538142
**[Test build #49383 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49383/consoleFull)**
for PR 10731 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10749#issuecomment-171539804
**[Test build #2380 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/2380/consoleFull)**
for PR 10749 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10658#issuecomment-171539964
**[Test build #49384 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49384/consoleFull)**
for PR 10658 at commit
Github user BenFradet commented on a diff in the pull request:
https://github.com/apache/spark/pull/10472#discussion_r49691297
--- Diff:
mllib/src/main/scala/org/apache/spark/ml/evaluation/BinaryClassificationEvaluator.scala
---
@@ -29,6 +29,7 @@ import
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/10753#issuecomment-171544854
What do we do if the user specifies "a.b" right now? I'd say we should
follow that, and make sure we have a test case for it.
---
If your project is set up for it, you
Github user zhichao-li commented on the pull request:
https://github.com/apache/spark/pull/10753#issuecomment-171544562
It would return attribute c in table b up on this patch. Any suggestion?
throw ambiguous exception for such case?ã
---
If your project is set up for it, you can
Github user maropu commented on the pull request:
https://github.com/apache/spark/pull/10427#issuecomment-171544801
@yhuai ping
---
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 commented on the pull request:
https://github.com/apache/spark/pull/10755#issuecomment-171544400
@viirya I took a stab at 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
Github user maropu commented on the pull request:
https://github.com/apache/spark/pull/10521#issuecomment-171544621
@andrewor14 ping
---
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/10735#issuecomment-171551238
**[Test build #2382 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/2382/consoleFull)**
for PR 10735 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10735#issuecomment-171551438
**[Test build #2381 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/2381/consoleFull)**
for PR 10735 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10703#issuecomment-171551693
**[Test build #49379 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49379/consoleFull)**
for PR 10703 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10752#issuecomment-171553465
**[Test build #49380 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49380/consoleFull)**
for PR 10752 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10752#issuecomment-171553634
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 gatorsmile commented on the pull request:
https://github.com/apache/spark/pull/10577#issuecomment-171560242
In this update, the major changes include
- Added a new analyzer rule `EliminateUnions` for remove the union with a
single child.
- Rewrote the function
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10577#issuecomment-171560133
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/10577#issuecomment-171560132
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 does
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/5827#issuecomment-171564759
@scwf are you guys using this feature? I'm thinking about just removing it
in Spark 2.0.
@chenghao-intel who wanted it in the first place no longer needs it.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10717#issuecomment-171530965
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/10717#issuecomment-171530961
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/10717#issuecomment-171530613
**[Test build #49372 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49372/consoleFull)**
for PR 10717 at commit
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/10751
---
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 zhichao-li opened a pull request:
https://github.com/apache/spark/pull/10753
[SPARK-12820]Resolve db.table.column
Currently spark only support to specify col name like: `table.col`, or
`col` in projection, but it's very common that user use `db.table.col`
especially
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10754#issuecomment-171535875
**[Test build #49382 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49382/consoleFull)**
for PR 10754 at commit
Github user sarutak commented on the pull request:
https://github.com/apache/spark/pull/10736#issuecomment-171535903
Very sorry for that. I missed to run `sbt scalastyle` with `-Pkinesis-asl`
on my local environment.
I wondered why the style checker passed in this PR and I found
Github user zhichao-li commented on a diff in the pull request:
https://github.com/apache/spark/pull/10731#discussion_r49689992
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/analysis/Analyzer.scala
---
@@ -441,7 +442,7 @@ class Analyzer(
//
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10735#issuecomment-171542072
**[Test build #2381 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/2381/consoleFull)**
for PR 10735 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10737#issuecomment-171542500
**[Test build #49378 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49378/consoleFull)**
for PR 10737 at commit
Github user viirya commented on the pull request:
https://github.com/apache/spark/pull/10755#issuecomment-171545714
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 sarutak commented on the pull request:
https://github.com/apache/spark/pull/10728#issuecomment-171546072
I found a needless semi-colon in ExecutorsPage.scala.
https://github.com/apache/spark/pull/10728/files#diff-e51a01ce10ed5c834e2f2a597fd02f2cR117
But
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10756#issuecomment-171546008
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10752#issuecomment-171553637
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/10731#issuecomment-171559762
**[Test build #49383 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49383/consoleFull)**
for PR 10731 at commit
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/10658#issuecomment-171565269
I've merged 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 does not have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10658#issuecomment-171565225
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/10658#issuecomment-171565086
**[Test build #49384 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49384/consoleFull)**
for PR 10658 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10658#issuecomment-171565226
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/10754#issuecomment-171565039
I will let @JoshRosen do this one.
---
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 sarutak opened a pull request:
https://github.com/apache/spark/pull/10754
[SPARK-12821][BUILD]Style checker should run when some configuration files
for style are modified but any source files are not.
When running the `run-tests` script, style checkers run only when
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/10658#issuecomment-171540733
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 Wenpei opened a pull request:
https://github.com/apache/spark/pull/10756
[SPARK-10264][Documentation] Added Since annotation for ml.recomendation
I create new pr since original pr long time no update.
Please help to review.
@srowen
You can merge this pull
Github user zhichao-li commented on the pull request:
https://github.com/apache/spark/pull/10753#issuecomment-171546245
Would return attribute b in table a. resolved within the logic of
`table.col`
---
If your project is set up for it, you can reply to this email and have your
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10596#issuecomment-171550842
**[Test build #49386 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49386/consoleFull)**
for PR 10596 at commit
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/10755#issuecomment-171549890
@viirya want to review 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
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/10703
---
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/10754#issuecomment-171558739
**[Test build #49382 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49382/consoleFull)**
for PR 10754 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10754#issuecomment-171559331
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/10754#issuecomment-171559329
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/10752#issuecomment-171560418
**[Test build #49390 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49390/consoleFull)**
for PR 10752 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10577#issuecomment-171560553
**[Test build #49391 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49391/consoleFull)**
for PR 10577 at commit
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/10658
---
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 JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/10637#issuecomment-171439930
LGTM. Thanks @carsonwang! I'm going to merge this into master and
branch-1.6.
---
If your project is set up for it, you can reply to this email and have your
reply
Github user JoshRosen commented on a diff in the pull request:
https://github.com/apache/spark/pull/10634#discussion_r49656738
--- Diff:
sql/core/src/main/java/org/apache/spark/sql/execution/UnsafeKVExternalSorter.java
---
@@ -125,7 +125,8 @@ public UnsafeKVExternalSorter(
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/9935#issuecomment-171451259
Actually, it looks like this has been taken over in #10635. @smola, do you
mind closing this in favor of the newer active PR? Thanks!
---
If your project is set up
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9263#issuecomment-171462138
**[Test build #49329 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49329/consoleFull)**
for PR 9263 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10703#issuecomment-171462187
**[Test build #49338 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49338/consoleFull)**
for PR 10703 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10728#issuecomment-171467753
**[Test build #49343 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49343/consoleFull)**
for PR 10728 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10703#issuecomment-171467932
**[Test build #49342 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49342/consoleFull)**
for PR 10703 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10724#issuecomment-171470894
**[Test build #2379 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/2379/consoleFull)**
for PR 10724 at commit
Github user marmbrus commented on a diff in the pull request:
https://github.com/apache/spark/pull/10745#discussion_r49668722
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/SqlParser.scala ---
@@ -1,509 +0,0 @@
-/*
- * Licensed to the Apache Software
Github user marmbrus commented on a diff in the pull request:
https://github.com/apache/spark/pull/10745#discussion_r49668661
--- Diff: sql/core/src/main/scala/org/apache/spark/sql/functions.scala ---
@@ -1063,7 +1063,7 @@ object functions extends LegacyFunctions {
*
Github user gliptak commented on a diff in the pull request:
https://github.com/apache/spark/pull/9263#discussion_r49668651
--- Diff: python/pyspark/mllib/tests.py ---
@@ -75,22 +75,23 @@
# No SciPy, but that's okay, we'll skip those tests
pass
-ser =
Github user yhuai commented on the pull request:
https://github.com/apache/spark/pull/10745#issuecomment-171474496
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 this
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10735#issuecomment-171474411
**[Test build #49348 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49348/consoleFull)**
for PR 10735 at commit
GitHub user marmbrus opened a pull request:
https://github.com/apache/spark/pull/10747
[SPARK-12813][SQL] Eliminate serialization for back to back operations
The goal of this PR is to eliminate unnecessary translations when there are
back-to-back `MapPartitions` operations. In
Github user marmbrus commented on the pull request:
https://github.com/apache/spark/pull/10747#issuecomment-171476290
/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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10604#issuecomment-171481518
**[Test build #49354 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49354/consoleFull)**
for PR 10604 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10604#issuecomment-171481526
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/10604#issuecomment-171481535
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 does
Github user marmbrus commented on a diff in the pull request:
https://github.com/apache/spark/pull/10567#discussion_r49672170
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/optimizer/Optimizer.scala
---
@@ -769,6 +770,79 @@ object ReorderJoin extends
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10604#issuecomment-171481261
**[Test build #49332 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49332/consoleFull)**
for PR 10604 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10703#issuecomment-171483525
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/10637
---
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 JoshRosen commented on a diff in the pull request:
https://github.com/apache/spark/pull/10585#discussion_r49654742
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/SparkListener.scala ---
@@ -293,6 +293,15 @@ class StatsReportListener extends SparkListener with
Github user JoshRosen commented on a diff in the pull request:
https://github.com/apache/spark/pull/7025#discussion_r49657198
--- Diff: R/pkg/R/client.R ---
@@ -42,6 +42,19 @@ determineSparkSubmitBin <- function() {
}
sparkSubmitBinName
}
+# R supports both
Github user nongli commented on a diff in the pull request:
https://github.com/apache/spark/pull/10703#discussion_r49657207
--- Diff:
sql/core/src/test/java/test/org/apache/spark/sql/JavaDatasetSuite.java ---
@@ -290,9 +290,7 @@ public void testSetOperation() {
List data
Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/10703#discussion_r49658126
--- Diff:
sql/core/src/test/java/test/org/apache/spark/sql/JavaDatasetSuite.java ---
@@ -290,9 +290,7 @@ public void testSetOperation() {
List
Github user nongli commented on a diff in the pull request:
https://github.com/apache/spark/pull/10604#discussion_r49658096
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/sources/interfaces.scala ---
@@ -683,9 +685,29 @@ abstract class HadoopFsRelation private[sql](
Github user vanzin commented on the pull request:
https://github.com/apache/spark/pull/10238#issuecomment-171451965
Yay, finally. Any comments anyone? Otherwise I'll push this soon-ish.
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/10604#discussion_r49660055
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/sources/interfaces.scala ---
@@ -683,9 +685,29 @@ abstract class HadoopFsRelation private[sql](
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10604#issuecomment-171461346
**[Test build #49336 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49336/consoleFull)**
for PR 10604 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10604#issuecomment-171461354
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/10604#issuecomment-171461052
**[Test build #49336 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49336/consoleFull)**
for PR 10604 at commit
Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/10604#discussion_r49662959
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/sources/interfaces.scala ---
@@ -683,9 +685,29 @@ abstract class HadoopFsRelation private[sql](
Github user nongli commented on a diff in the pull request:
https://github.com/apache/spark/pull/10604#discussion_r49664183
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/sources/interfaces.scala ---
@@ -683,9 +685,29 @@ abstract class HadoopFsRelation private[sql](
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10744#issuecomment-171463291
**[Test build #49340 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49340/consoleFull)**
for PR 10744 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10744#issuecomment-171467356
**[Test build #49340 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49340/consoleFull)**
for PR 10744 at commit
301 - 400 of 746 matches
Mail list logo
