Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10494#issuecomment-167515530
**[Test build #48361 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48361/consoleFull)**
for PR 10494 at commit
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/10350
---
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 srowen commented on the pull request:
https://github.com/apache/spark/pull/10434#issuecomment-167540865
OK, either way. I was suggesting that it's fine to make this example
consistent with the others, even if test/train isn't the point of this example.
if you do proceed,
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/10350#issuecomment-167540772
Merged to 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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10402#issuecomment-167542344
**[Test build #48363 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48363/consoleFull)**
for PR 10402 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10402#issuecomment-167542409
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/10402#issuecomment-167542410
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user vectorijk commented on a diff in the pull request:
https://github.com/apache/spark/pull/10488#discussion_r48475242
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/misc.scala
---
@@ -57,9 +57,10 @@ case class Md5(child: Expression)
Github user WangTaoTheTonic commented on the pull request:
https://github.com/apache/spark/pull/10238#issuecomment-167507929
Sorry for late. Think you need update codes to the newest and see if the
test cases fine.
Then we do some review and function tests.
---
If your project
GitHub user gatorsmile opened a pull request:
https://github.com/apache/spark/pull/10494
[SPARK-12536][SQL]Added "Empty Seq" in Explain Outputs For Empty
LocalRelation and LocalTableScan
The filter `Filter (False)` generates an empty `LocalRelation` in
`SimplifyFilters`. In the
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/10465
---
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 srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/10381#discussion_r48472333
--- Diff: mllib/src/test/scala/org/apache/spark/ml/param/ParamsSuite.scala
---
@@ -349,6 +352,41 @@ class ParamsSuite extends SparkFunSuite {
val t3
Github user hvanhovell commented on the pull request:
https://github.com/apache/spark/pull/10488#issuecomment-167540178
@yhuai can you take a look 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
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/10252#issuecomment-167541007
Before reviewing this further, let's return to the JIRA. I do not see that
this implements something that you a) can't do with updateStateByKey or
trackStateByKey, or
Github user sarutak commented on a diff in the pull request:
https://github.com/apache/spark/pull/10381#discussion_r48473237
--- Diff: mllib/src/test/scala/org/apache/spark/ml/param/ParamsSuite.scala
---
@@ -349,6 +352,41 @@ class ParamsSuite extends SparkFunSuite {
val
Github user sun-rui commented on a diff in the pull request:
https://github.com/apache/spark/pull/10480#discussion_r48467198
--- Diff: R/pkg/R/DataFrame.R ---
@@ -2272,3 +2260,40 @@ setMethod("with",
newEnv <- assignNewEnv(data)
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/10442#discussion_r48467535
--- Diff: pom.xml ---
@@ -99,14 +99,14 @@
sql/hive
unsafe
assembly
-external/twitter
-external/flume
-
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/10465#issuecomment-167538830
Merged to 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 sun-rui commented on a diff in the pull request:
https://github.com/apache/spark/pull/10480#discussion_r48472220
--- Diff: R/pkg/R/SQLContext.R ---
@@ -556,3 +556,61 @@ createExternalTable <- function(sqlContext, tableName,
path = NULL, source = NUL
sdf <-
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10381#issuecomment-167544609
**[Test build #48364 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48364/consoleFull)**
for PR 10381 at commit
Github user Cazen closed the pull request at:
https://github.com/apache/spark/pull/10496
---
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 viirya commented on the pull request:
https://github.com/apache/spark/pull/10391#issuecomment-167585649
@cloud-fan Can you also review the updates? 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 srowen commented on the pull request:
https://github.com/apache/spark/pull/10413#issuecomment-167564115
@rxin I wanted to sound you out on this one -- do you feel strongly against
it or are the reasons above a little persuasive?
---
If your project is set up for it, you
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10496#issuecomment-167566226
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 Cazen opened a pull request:
https://github.com/apache/spark/pull/10497
[SPARK-12537] [SQL] Add option to accept quoting of all character backslash
quoting mechanism
We can provides the option to choose JSON parser can be enabled to accept
quoting of all character or
Github user Cazen commented on the pull request:
https://github.com/apache/spark/pull/10497#issuecomment-167585156
recreate pull request(10496->10497)
---
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 viirya commented on a diff in the pull request:
https://github.com/apache/spark/pull/10401#discussion_r48483901
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/ScalaReflection.scala
---
@@ -407,10 +407,13 @@ object ScalaReflection extends
Github user viirya commented on a diff in the pull request:
https://github.com/apache/spark/pull/10401#discussion_r48483879
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/ScalaReflection.scala
---
@@ -407,10 +407,13 @@ object ScalaReflection extends
GitHub user Cazen opened a pull request:
https://github.com/apache/spark/pull/10495
[SPARK-12537][SQL] Add option to accept quoting of all character backslash
quoting mechanism
We can provides the option to choose JSON parser can be enabled to accept
quoting of all character or
Github user Cazen closed the pull request at:
https://github.com/apache/spark/pull/10495
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10497#issuecomment-167573953
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 hvanhovell commented on a diff in the pull request:
https://github.com/apache/spark/pull/10488#discussion_r48479722
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/misc.scala
---
@@ -57,9 +57,10 @@ case class Md5(child: Expression)
Github user viirya commented on the pull request:
https://github.com/apache/spark/pull/10401#issuecomment-167578551
ping @marmbrus @davies @cloud-fan Can you see if this patch is ok to merge?
Thanks.
---
If your project is set up for it, you can reply to this email and have your
Github user cloud-fan commented on the pull request:
https://github.com/apache/spark/pull/10498#issuecomment-167581087
cc @yhuai @nongli
---
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 cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/10401#discussion_r48482886
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/ScalaReflection.scala
---
@@ -407,10 +407,13 @@ object ScalaReflection extends
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/10497#issuecomment-167585890
In general you do not need to open a new pull request. But before you make
a PR, best to finish the questions on the JIRA. I'm not yet clear why this is
regularly
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10446#issuecomment-167566796
**[Test build #48366 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48366/consoleFull)**
for PR 10446 at commit
Github user pjfanning commented on a diff in the pull request:
https://github.com/apache/spark/pull/10403#discussion_r48481306
--- Diff:
docker-integration-tests/src/test/scala/org/apache/spark/sql/jdbc/MySQLIntegrationSuite.scala
---
@@ -150,4 +150,91 @@ class
Github user viirya commented on the pull request:
https://github.com/apache/spark/pull/10330#issuecomment-167578659
ping @marmbrus @yhuai Please help see if this patch is ok for you. Thanks.
---
If your project is set up for it, you can reply to this email and have your
reply appear
GitHub user Cazen opened a pull request:
https://github.com/apache/spark/pull/10496
[SPARK-12537] [SQL] Add option to accept quoting of all character backslash
quoting mechanism
We can provides the option to choose JSON parser can be enabled to accept
quoting of all character or
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10413#issuecomment-167565889
**[Test build #48365 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48365/consoleFull)**
for PR 10413 at commit
Github user Cazen commented on the pull request:
https://github.com/apache/spark/pull/10496#issuecomment-167571045
For example, if JSON file that includes not listed by JSON backslash
quoting specification, it returns corrupt_record
JSON File
{"name": "Cazen Lee", "price":
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10498#issuecomment-167582335
**[Test build #48367 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48367/consoleFull)**
for PR 10498 at commit
Github user cloud-fan commented on the pull request:
https://github.com/apache/spark/pull/10435#issuecomment-167583523
need some help about the R test, I can't see the expected result through
the error log...
---
If your project is set up for it, you can reply to this email and have
Github user viirya closed the pull request at:
https://github.com/apache/spark/pull/10401
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10495#issuecomment-167564428
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 cloud-fan opened a pull request:
https://github.com/apache/spark/pull/10498
[SPARK-12539][SQL][WIP] support writing bucketed table
Done:
* add bucket info in write path
* support writing bucketed `HadoopFsRelation`
TODO:
* figure out a way
Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/10435#discussion_r48482588
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/misc.scala
---
@@ -176,3 +178,221 @@ case class Crc32(child: Expression)
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10446#issuecomment-167590960
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/10446#issuecomment-167590880
**[Test build #48366 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48366/consoleFull)**
for PR 10446 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10446#issuecomment-167590962
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/8785#discussion_r48492460
--- Diff:
sql/core/src/test/scala/org/apache/spark/sql/jdbc/UnserializableDriverHelper.scala
---
@@ -0,0 +1,53 @@
+/*
+ * Licensed to the Apache
Github user yhuai commented on the pull request:
https://github.com/apache/spark/pull/10498#issuecomment-167614005
This one also includes https://github.com/apache/spark/pull/10435, right?
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user yhuai commented on a diff in the pull request:
https://github.com/apache/spark/pull/10402#discussion_r48495547
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/windowExpressions.scala
---
@@ -327,9 +327,9 @@ abstract class
Github user hvanhovell commented on a diff in the pull request:
https://github.com/apache/spark/pull/10402#discussion_r48495956
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/windowExpressions.scala
---
@@ -327,9 +327,9 @@ abstract class
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10498#issuecomment-167596712
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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/10377
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10413#issuecomment-167591723
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/10413#issuecomment-167591612
**[Test build #48365 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48365/consoleFull)**
for PR 10413 at commit
Github user tribbloid commented on a diff in the pull request:
https://github.com/apache/spark/pull/8785#discussion_r48489063
--- Diff:
sql/core/src/test/scala/org/apache/spark/sql/jdbc/UnserializableDriverHelper.scala
---
@@ -0,0 +1,53 @@
+/*
+ * Licensed to the Apache
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10413#issuecomment-167591724
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user yhuai commented on the pull request:
https://github.com/apache/spark/pull/10377#issuecomment-167601702
LGTM. Merging to 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
Github user marmbrus commented on the pull request:
https://github.com/apache/spark/pull/10452#issuecomment-167605425
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
Github user yhuai commented on a diff in the pull request:
https://github.com/apache/spark/pull/10330#discussion_r48494801
--- Diff:
sql/core/src/test/scala/org/apache/spark/sql/execution/RowFormatConvertersSuite.scala
---
@@ -38,7 +38,7 @@ class RowFormatConvertersSuite extends
Github user yhuai commented on a diff in the pull request:
https://github.com/apache/spark/pull/10488#discussion_r48495327
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/misc.scala
---
@@ -57,9 +57,10 @@ case class Md5(child: Expression) extends
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10498#issuecomment-167596617
**[Test build #48367 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48367/consoleFull)**
for PR 10498 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10498#issuecomment-167596714
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user yhuai commented on the pull request:
https://github.com/apache/spark/pull/10435#issuecomment-167614804
I see
```
1. Failure (at test_sparkSQL.R#1160): group by, agg functions
--
30 not equal to collect(max(gd))[1, 2]
30 - 19 == 11
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/10393
---
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 sarutak commented on the pull request:
https://github.com/apache/spark/pull/10487#issuecomment-167653173
@QiangCai LGTM but could you add test cases?
---
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 ted-yu opened a pull request:
https://github.com/apache/spark/pull/10499
[DOC] Adjust coverage for partitionBy()
This is the related thread:
http://search-hadoop.com/m/q3RTtO3ReeJ1iF02=Re+partitioning+json+data+in+spark
Michael suggested fixing the doc.
Github user marmbrus commented on the pull request:
https://github.com/apache/spark/pull/10393#issuecomment-167651518
Thanks, merging to 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
Github user zsxwing commented on a diff in the pull request:
https://github.com/apache/spark/pull/10459#discussion_r48505634
--- Diff: core/src/test/scala/org/apache/spark/util/AkkaUtilsSuite.scala ---
@@ -61,9 +55,14 @@ class AkkaUtilsSuite extends SparkFunSuite with
Github user zsxwing commented on a diff in the pull request:
https://github.com/apache/spark/pull/10368#discussion_r48507496
--- Diff:
core/src/main/scala/org/apache/spark/serializer/KryoSerializer.scala ---
@@ -109,6 +111,9 @@ class KryoSerializer(conf: SparkConf)
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/10471#discussion_r48507936
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/commands.scala ---
@@ -102,6 +102,7 @@ case class SetCommand(kv: Option[(String,
Github user zsxwing commented on a diff in the pull request:
https://github.com/apache/spark/pull/10368#discussion_r48508806
--- Diff:
core/src/main/scala/org/apache/spark/serializer/KryoSerializer.scala ---
@@ -109,6 +111,9 @@ class KryoSerializer(conf: SparkConf)
Github user JoshRosen commented on a diff in the pull request:
https://github.com/apache/spark/pull/10499#discussion_r48508973
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/DataFrameWriter.scala ---
@@ -119,7 +119,7 @@ final class DataFrameWriter private[sql](df:
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10499#issuecomment-167670012
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/10499#issuecomment-167670013
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/10499#issuecomment-167669938
**[Test build #48373 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48373/consoleFull)**
for PR 10499 at commit
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/10440#issuecomment-167672081
Maybe @yhuai or @liancheng should take a quick look at the SQL changes.
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10479#issuecomment-167673716
**[Test build #48376 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48376/consoleFull)**
for PR 10479 at commit
Github user andrewor14 commented on a diff in the pull request:
https://github.com/apache/spark/pull/10368#discussion_r48511217
--- Diff:
core/src/main/scala/org/apache/spark/serializer/KryoSerializer.scala ---
@@ -109,6 +111,9 @@ class KryoSerializer(conf: SparkConf)
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10479#issuecomment-167673765
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/10479#issuecomment-167673766
Test PASSed.
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/10479
---
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 andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/10368#issuecomment-167673871
As @zsxwing pointed out, the existing unit tests are not sufficient because
they didn't catch the fact that `ShuffleReadMetrics` et al must also be
registered. This
Github user yhuai commented on the pull request:
https://github.com/apache/spark/pull/10440#issuecomment-167675193
sql changes look 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
Github user zsxwing commented on the pull request:
https://github.com/apache/spark/pull/10440#issuecomment-167675496
Thanks. Merging to master and 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 your project does
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10441#issuecomment-167675687
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 JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/10441#issuecomment-167675703
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10441#issuecomment-167675690
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user gatorsmile commented on the pull request:
https://github.com/apache/spark/pull/10393#issuecomment-167675761
Thank you!
---
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 JoshRosen commented on a diff in the pull request:
https://github.com/apache/spark/pull/10441#discussion_r48511839
--- Diff: core/src/main/scala/org/apache/spark/ui/jobs/StagePage.scala ---
@@ -1232,24 +1243,16 @@ private[ui] class TaskPagedTable(
override
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/10440
---
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 viirya closed the pull request at:
https://github.com/apache/spark/pull/10251
---
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 squito commented on the pull request:
https://github.com/apache/spark/pull/6935#issuecomment-167676684
hi @steveloughran , I think maybe some commits didn't get pushed? I
noticed a few places where things didn't seem to quite line up to your
comments. (also there is a
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10438#issuecomment-167676871
**[Test build #48374 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48374/consoleFull)**
for PR 10438 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10438#issuecomment-167676897
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/10438#issuecomment-167676895
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
101 - 200 of 418 matches
Mail list logo
