Github user sameeragarwal commented on a diff in the pull request:
https://github.com/apache/spark/pull/12194#discussion_r64495331
--- Diff:
sql/hive/src/main/scala/org/apache/spark/sql/hive/execution/ScriptTransformation.scala
---
@@ -127,45 +127,78 @@ case class
Github user zsxwing commented on a diff in the pull request:
https://github.com/apache/spark/pull/13286#discussion_r64495145
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/streaming/memory.scala
---
@@ -114,35 +114,48 @@ case class MemoryStream[A : Encoder](id:
Github user zsxwing commented on a diff in the pull request:
https://github.com/apache/spark/pull/13286#discussion_r64495148
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/streaming/memory.scala
---
@@ -114,35 +114,48 @@ case class MemoryStream[A : Encoder](id:
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13265#issuecomment-221435889
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/13265#issuecomment-221435892
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/13265#issuecomment-221435811
**[Test build #59233 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/59233/consoleFull)**
for PR 13265 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13272#issuecomment-221435767
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/13272#issuecomment-221435765
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/13272#issuecomment-221435650
**[Test build #59225 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/59225/consoleFull)**
for PR 13272 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13282#issuecomment-221435298
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 zsxwing commented on a diff in the pull request:
https://github.com/apache/spark/pull/13286#discussion_r64494863
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/ContinuousQueryManager.scala ---
@@ -175,9 +175,9 @@ class ContinuousQueryManager(sparkSession:
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/13282#issuecomment-221435340
**[Test build #59237 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/59237/consoleFull)**
for PR 13282 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/13286#issuecomment-221435335
**[Test build #59236 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/59236/consoleFull)**
for PR 13286 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13282#issuecomment-221435299
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user dongjoon-hyun commented on the pull request:
https://github.com/apache/spark/pull/13282#issuecomment-221435072
It seems not necessary since this PR prevents at the level of `Repartition`
ctor.
```
case class Repartition(numPartitions: Int, shuffle: Boolean, child:
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13286#issuecomment-221434083
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/13286#issuecomment-221434079
**[Test build #59235 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/59235/consoleFull)**
for PR 13286 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13286#issuecomment-221434090
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/13286#issuecomment-221433717
**[Test build #59235 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/59235/consoleFull)**
for PR 13286 at commit
Github user xwu0226 commented on the pull request:
https://github.com/apache/spark/pull/13276#issuecomment-221432018
I have tried mvn build and test with the build/mvn commands used in jenkins
jobs for hadoop 2.2, ..., 2.7 and can not recreate the test case failure on my
environment.
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/13282#issuecomment-221431790
CheckAnalysis?
---
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/13282#issuecomment-221431220
**[Test build #59234 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/59234/consoleFull)**
for PR 13282 at commit
Github user dongjoon-hyun commented on the pull request:
https://github.com/apache/spark/pull/13282#issuecomment-221431064
Hi, @rxin .
I added that to catalyst/DataSetSuite/DataFrameSuite, too.
So far, I cannot find a proper place in Analyzer. If you mind, could you
give me
Github user tdas commented on a diff in the pull request:
https://github.com/apache/spark/pull/13286#discussion_r64492042
--- Diff:
sql/core/src/test/scala/org/apache/spark/sql/streaming/StreamingAggregationSuite.scala
---
@@ -67,6 +64,43 @@ class StreamingAggregationSuite
Github user davies commented on a diff in the pull request:
https://github.com/apache/spark/pull/13155#discussion_r64491862
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/optimizer/Optimizer.scala
---
@@ -1695,16 +1695,176 @@ object
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/13265#issuecomment-221429580
**[Test build #59233 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/59233/consoleFull)**
for PR 13265 at commit
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/13265#discussion_r64491192
--- Diff:
mllib/src/main/scala/org/apache/spark/mllib/optimization/GradientDescent.scala
---
@@ -197,6 +197,11 @@ object GradientDescent extends Logging {
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13286#issuecomment-221429134
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 srowen commented on the pull request:
https://github.com/apache/spark/pull/13265#issuecomment-221429135
Jenkins test this please
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13286#issuecomment-221429136
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/13286#issuecomment-221429129
**[Test build #59232 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/59232/consoleFull)**
for PR 13286 at commit
Github user tdas commented on a diff in the pull request:
https://github.com/apache/spark/pull/13286#discussion_r64490957
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/streaming/StatefulAggregate.scala
---
@@ -82,40 +82,60 @@ case class StateStoreRestoreExec(
Github user tdas commented on a diff in the pull request:
https://github.com/apache/spark/pull/13286#discussion_r64490915
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/streaming/IncrementalExecution.scala
---
@@ -35,15 +35,36 @@ class IncrementalExecution
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/13280#issuecomment-221428658
The dev/test-dependencies script can auto update the deps files for this
purpose.
One thing we ask people to investigate are changes between old and new
Github user GayathriMurali commented on the pull request:
https://github.com/apache/spark/pull/13285#issuecomment-221428716
@jkbradley @MLnick I have marked this WIP, as I want to get your thoughts
on if you think the format looks ok. I can add examples to KMeans and SurvReg
is the
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13285#issuecomment-221428651
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/13286#issuecomment-221428703
**[Test build #59232 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/59232/consoleFull)**
for PR 13286 at commit
Github user tdas commented on a diff in the pull request:
https://github.com/apache/spark/pull/13286#discussion_r64490597
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/aggregate/utils.scala ---
@@ -311,8 +313,9 @@ object Utils {
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13270#issuecomment-221428304
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/13270#issuecomment-221428305
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/13270#issuecomment-221428174
**[Test build #59224 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/59224/consoleFull)**
for PR 13270 at commit
Github user tdas commented on a diff in the pull request:
https://github.com/apache/spark/pull/13286#discussion_r64490566
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/aggregate/utils.scala ---
@@ -33,7 +34,7 @@ object Utils {
resultExpressions:
Github user tdas commented on a diff in the pull request:
https://github.com/apache/spark/pull/13286#discussion_r64490527
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/DataFrameWriter.scala ---
@@ -77,7 +77,50 @@ final class DataFrameWriter private[sql](df: DataFrame) {
Github user tdas commented on a diff in the pull request:
https://github.com/apache/spark/pull/13286#discussion_r64490460
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/analysis/UnsupportedOperationChecker.scala
---
@@ -55,21 +56,6 @@ object
Github user tdas commented on a diff in the pull request:
https://github.com/apache/spark/pull/13286#discussion_r64490480
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/analysis/UnsupportedOperationChecker.scala
---
@@ -55,21 +56,6 @@ object
GitHub user GayathriMurali opened a pull request:
https://github.com/apache/spark/pull/13285
[Spark 15129][R][DOC][WIP]R API changes in ML
## What changes were proposed in this pull request?
Make user guide changes to SparkR documentation for all changes that
happened in
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/13273#issuecomment-221427808
**[Test build #59231 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/59231/consoleFull)**
for PR 13273 at commit
GitHub user tdas opened a pull request:
https://github.com/apache/spark/pull/13286
[SPARK-15517][SQL][STREAMING] Add support for complete output mode in
Structure Streaming
## What changes were proposed in this pull request?
Currently structured streaming only supports append
Github user cloud-fan commented on the pull request:
https://github.com/apache/spark/pull/13273#issuecomment-221427461
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13284#issuecomment-221426358
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/13284#issuecomment-221426332
**[Test build #59228 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/59228/consoleFull)**
for PR 13284 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13284#issuecomment-221426362
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user dongjoon-hyun commented on the pull request:
https://github.com/apache/spark/pull/13282#issuecomment-221426314
Yes. They need this. I'll add 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 your
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/13107#issuecomment-221426056
Should we have a default value that's not Long.MAX_VALUE for this? What
values do you guys typically set?
---
If your project is set up for it, you can reply to this
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13273#issuecomment-221425454
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/13273#issuecomment-221425457
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/13273#issuecomment-221425436
**[Test build #59230 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/59230/consoleFull)**
for PR 13273 at commit
Github user dongjoon-hyun commented on the pull request:
https://github.com/apache/spark/pull/13282#issuecomment-221425046
Thank you for review, @rxin .
I'll check them whether they need this.
---
If your project is set up for it, you can reply to this email and have your
reply
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/13282#issuecomment-221424583
Can we add these to the dataframe API? And in the analyzer?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user xwu0226 commented on a diff in the pull request:
https://github.com/apache/spark/pull/13270#discussion_r64488208
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/command/createDataSourceTables.scala
---
@@ -385,7 +385,10 @@ object
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/13273#issuecomment-221423945
**[Test build #59230 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/59230/consoleFull)**
for PR 13273 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13139#issuecomment-221423564
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/13139#issuecomment-221423561
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/13139#issuecomment-221423464
**[Test build #59227 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/59227/consoleFull)**
for PR 13139 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/13283#issuecomment-221422916
**[Test build #59229 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/59229/consoleFull)**
for PR 13283 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/13284#issuecomment-221422898
**[Test build #59228 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/59228/consoleFull)**
for PR 13284 at commit
GitHub user wangmiao1981 opened a pull request:
https://github.com/apache/spark/pull/13284
[SPARK-15439][SparkR]:Failed to run unit test in SparkR
## What changes were proposed in this pull request?
(Please fill in changes proposed in this fix)
There are some failures
GitHub user gatorsmile opened a pull request:
https://github.com/apache/spark/pull/13283
[SPARK-15515] [SPARK-15514] [SQL] Error Handling in Running SQL Directly On
Files
What changes were proposed in this pull request?
This PR is to address the following issues:
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/13139#issuecomment-221421942
**[Test build #59227 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/59227/consoleFull)**
for PR 13139 at commit
Github user sethah commented on the pull request:
https://github.com/apache/spark/pull/13139#issuecomment-221421289
@jkbradley I updated the notation to fall in line with Wikipedia.
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user hvanhovell commented on the pull request:
https://github.com/apache/spark/pull/13155#issuecomment-221419331
@frreiss this looks promising. I will take a more in depth look at it
tomorrow evening (GMT).
---
If your project is set up for it, you can reply to this email and
Github user xwu0226 commented on a diff in the pull request:
https://github.com/apache/spark/pull/13270#discussion_r64485252
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/catalog/SessionCatalog.scala
---
@@ -216,7 +216,25 @@ class SessionCatalog(
Github user andrewor14 commented on a diff in the pull request:
https://github.com/apache/spark/pull/13264#discussion_r64485134
--- Diff: core/src/main/scala/org/apache/spark/ui/storage/StorageTab.scala
---
@@ -59,7 +59,15 @@ class StorageListener(storageStatusListener:
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13271#issuecomment-221418603
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/13271#issuecomment-221418602
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/13271#issuecomment-221418413
**[Test build #59221 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/59221/consoleFull)**
for PR 13271 at commit
Github user gatorsmile commented on the pull request:
https://github.com/apache/spark/pull/12772#issuecomment-221418408
Sure, will do it. 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
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/12772#issuecomment-221418110
cc @gatorsmile would you be able to take this over and add a test case?
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/13280#issuecomment-221417951
cc @liancheng who might have idea about past parquet perf regressions.
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/13280#issuecomment-221417895
Yea you would need to explicitly update the dependency list. We added that
as a safe-guard to accidentally changing dependencies.
---
If your project is set up for it,
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/13150#issuecomment-221417642
This looks good. Just two minor nits. If you can fix those that would be
great.
Also - would it be possible to add a test case?
---
If your project is set up
Github user rdblue commented on the pull request:
https://github.com/apache/spark/pull/13280#issuecomment-221417279
I'm not sure what should be done to fix the dependency test failure. Looks
like there's a list of dependencies that needs to be updated. Is that something
I should
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/13150#discussion_r64484127
--- Diff:
sql/hive/src/main/scala/org/apache/spark/sql/hive/MetastoreRelation.scala ---
@@ -114,17 +117,31 @@ private[hive] case class MetastoreRelation(
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/13253#issuecomment-221416716
Yes definitely want to be able to read/write empty dfs.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well.
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/13272#issuecomment-221416475
**[Test build #59225 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/59225/consoleFull)**
for PR 13272 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8559#issuecomment-221416491
**[Test build #59226 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/59226/consoleFull)**
for PR 8559 at commit
Github user vanzin commented on the pull request:
https://github.com/apache/spark/pull/13272#issuecomment-221415791
hmm, that's working locally for me... 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.
Github user HyukjinKwon commented on the pull request:
https://github.com/apache/spark/pull/13253#issuecomment-221415292
Closing this. But could I please ask if it is basically perfered to support
to wrtie and read empty data back for all data sources and others (or maybe
Parquet,
Github user HyukjinKwon closed the pull request at:
https://github.com/apache/spark/pull/13253
---
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/13270#issuecomment-221415230
**[Test build #59224 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/59224/consoleFull)**
for PR 13270 at commit
Github user gt-rocker commented on a diff in the pull request:
https://github.com/apache/spark/pull/10187#discussion_r64482514
--- Diff:
core/src/main/scala/org/apache/spark/metrics/sink/OpenTsdbSink.scala ---
@@ -0,0 +1,165 @@
+/*
+ * Licensed to the Apache Software
Github user markhamstra commented on the pull request:
https://github.com/apache/spark/pull/8559#issuecomment-221414334
@squito Yeah, that's fine. I haven't gone through the new tests closely to
make sure that they are doing what they say they are doing, but the changes to
both
Github user liancheng commented on a diff in the pull request:
https://github.com/apache/spark/pull/13270#discussion_r64482317
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/catalog/SessionCatalog.scala
---
@@ -216,7 +216,25 @@ class SessionCatalog(
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/13282#issuecomment-221414021
**[Test build #59223 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/59223/consoleFull)**
for PR 13282 at commit
Github user squito commented on the pull request:
https://github.com/apache/spark/pull/8559#issuecomment-221413402
@markhamstra alright, in that case do you have any objections if I merge
this, one commit back? I'll throw in a comment on DummyExternalClusterManager
pointing to
GitHub user dongjoon-hyun opened a pull request:
https://github.com/apache/spark/pull/13282
[SPARK-15512][CORE] repartition(0) should raise IllegalArgumentException
## What changes were proposed in this pull request?
Previously, SPARK-8893 added the constraints on positive
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13272#issuecomment-221412501
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/13272#issuecomment-221412499
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/13272#issuecomment-221412265
**[Test build #59218 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/59218/consoleFull)**
for PR 13272 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13176#issuecomment-221410132
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
201 - 300 of 664 matches
Mail list logo
