Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16784
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 project does not have this feature
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16784
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/72312/
Test FAILed.
---
Github user gatorsmile commented on a diff in the pull request:
https://github.com/apache/spark/pull/16269#discussion_r99394346
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/SparkStrategies.scala ---
@@ -405,32 +405,4 @@ abstract class SparkStrategies extends
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15770
**[Test build #72313 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72313/testReport)**
for PR 15770 at commit
Github user liancheng commented on the issue:
https://github.com/apache/spark/pull/16791
cc @cloud-fan @rxin @HyukjinKwon
---
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 dongjoon-hyun commented on the issue:
https://github.com/apache/spark/pull/16751
Ur, I reproduce that with maven test.
It's about test dependency on `parquet-avro` which now depends on
`org.apache.avro` 1.8.0.
---
If your project is set up for it, you can reply to
Github user liancheng commented on the issue:
https://github.com/apache/spark/pull/16791
@dongjoon-hyun Actually, could you please point me the Maven build failure?
I don't think this failure is caused by this PR, is it? Are you refering to
some existing PR introduced by some earlier
Github user sethah commented on a diff in the pull request:
https://github.com/apache/spark/pull/16740#discussion_r99407439
--- Diff:
mllib/src/main/scala/org/apache/spark/ml/regression/GeneralizedLinearRegression.scala
---
@@ -335,6 +335,11 @@ class GeneralizedLinearRegression
Github user sethah commented on a diff in the pull request:
https://github.com/apache/spark/pull/16740#discussion_r99408646
--- Diff:
mllib/src/test/scala/org/apache/spark/ml/regression/GeneralizedLinearRegressionSuite.scala
---
@@ -743,6 +744,50 @@ class
Github user sethah commented on a diff in the pull request:
https://github.com/apache/spark/pull/16740#discussion_r99413491
--- Diff:
mllib/src/main/scala/org/apache/spark/ml/optim/IterativelyReweightedLeastSquares.scala
---
@@ -89,7 +89,7 @@ private[ml] class
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16686
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 does not have this feature
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16793
**[Test build #72318 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72318/testReport)**
for PR 16793 at commit
Github user salilsurendran commented on a diff in the pull request:
https://github.com/apache/spark/pull/16664#discussion_r99414739
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/DataFrameWriter.scala ---
@@ -428,8 +481,14 @@ final class DataFrameWriter[T] private[sql](ds:
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16787
**[Test build #72310 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72310/testReport)**
for PR 16787 at commit
GitHub user actuaryzhang opened a pull request:
https://github.com/apache/spark/pull/16794
[SPARK-19452][SparkR] Fix bug in the name assignment method
## What changes were proposed in this pull request?
The names method fails to check for validity of the assignment values. This
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16793
**[Test build #72319 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72319/testReport)**
for PR 16793 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16757
**[Test build #72323 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72323/testReport)**
for PR 16757 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16794
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 project does not have this feature
Github user zero323 commented on the issue:
https://github.com/apache/spark/pull/16792
cc @rxin, @holdenk
---
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,
GitHub user zero323 opened a pull request:
https://github.com/apache/spark/pull/16793
[SPARK-19454][PYTHON][SQL] DataFrame.replace improvements
## What changes were proposed in this pull request?
- Allows skipping `value` argument if `to_replace` is a `dict`:
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16793
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/72318/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16793
**[Test build #72318 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72318/testReport)**
for PR 16793 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16787
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/72310/
Test FAILed.
---
Github user gatorsmile commented on a diff in the pull request:
https://github.com/apache/spark/pull/16664#discussion_r99415847
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/internal/SQLConf.scala ---
@@ -660,12 +660,21 @@ object SQLConf {
.booleanConf
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16787
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 project does not have this feature
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16686
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/72316/
Test PASSed.
---
Github user gatorsmile commented on a diff in the pull request:
https://github.com/apache/spark/pull/16664#discussion_r99416910
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/DataFrameWriter.scala ---
@@ -428,8 +481,14 @@ final class DataFrameWriter[T] private[sql](ds:
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16792
**[Test build #72317 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72317/testReport)**
for PR 16792 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16795
**[Test build #72322 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72322/testReport)**
for PR 16795 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16793
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/72319/
Test PASSed.
---
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/16737
: ) When @sureshthalamati tried to fix the docker test failure in Oracle,
he found the new code change in Spark 2.1 makes JDBC option key values always
lower case. However, Oracle's connection
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16791
**[Test build #72315 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72315/testReport)**
for PR 16791 at commit
Github user dongjoon-hyun commented on the issue:
https://github.com/apache/spark/pull/16795
Thank you for review, @jaceklaskowski . Yep. I made this first because that
means more.
Actually, I'm running another maven test for that, `bumping avro to 1.8.1`,
too.
If that pass,
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16796
**[Test build #72325 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72325/testReport)**
for PR 16796 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16784
**[Test build #72314 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72314/testReport)**
for PR 16784 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16784
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 does not have this feature
GitHub user zero323 opened a pull request:
https://github.com/apache/spark/pull/16792
[SPARK-19453][PYTHON][SQL][DOC] Correct and extend DataFrame.replace
docstring
## What changes were proposed in this pull request?
- Provides correct description of the semantics of a
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16686
**[Test build #72316 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72316/testReport)**
for PR 16686 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16792
**[Test build #72317 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72317/testReport)**
for PR 16792 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16793
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 does not have this feature
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16793
**[Test build #72319 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72319/testReport)**
for PR 16793 at commit
Github user squito commented on the issue:
https://github.com/apache/spark/pull/16620
Hi @jinxing64
I'm sorry I haven't had time to look again. So the one big concern I had
was still that test case -- I know you fixed up some of the things I complained
about, but I still
GitHub user rxin opened a pull request:
https://github.com/apache/spark/pull/16796
[SPARK-10063] Follow-up: remove dead code related to an old output
committer.
## What changes were proposed in this pull request?
DirectParquetOutputCommitter was removed from Spark as it was
Github user felixcheung commented on the issue:
https://github.com/apache/spark/pull/16767
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 feature
enabled and wishes
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/16767
---
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 issue:
https://github.com/apache/spark/pull/16626
**[Test build #72320 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72320/testReport)**
for PR 16626 at commit
Github user kayousterhout commented on the issue:
https://github.com/apache/spark/pull/16738
I'd prefer to just change the log message and not rename successful to
completed -- which I think is too ambiguous with tasks that have "completed" in
the sense that they've failed (if we're
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16792
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/72317/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16792
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 does not have this feature
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16783
**[Test build #72324 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72324/testReport)**
for PR 16783 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16794
**[Test build #72321 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72321/testReport)**
for PR 16794 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16794
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/72321/
Test FAILed.
---
Github user zero323 commented on the issue:
https://github.com/apache/spark/pull/16792
Thanks @rxin.
This is related to #16793 /
[SPARK-19454](https://issues.apache.org/jira/browse/SPARK-19454)
---
If your project is set up for it, you can reply to this email and have your
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16784
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/72314/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16686
**[Test build #72316 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72316/testReport)**
for PR 16686 at commit
Github user gatorsmile commented on a diff in the pull request:
https://github.com/apache/spark/pull/16664#discussion_r99415540
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/DataFrameWriter.scala ---
@@ -190,6 +192,32 @@ final class DataFrameWriter[T] private[sql](ds:
Github user actuaryzhang commented on the issue:
https://github.com/apache/spark/pull/16794
An example illustrating the issue:
```
df <- suppressWarnings(createDataFrame(iris))
# this is error
colnames(df) <- NULL
# this should report error
names(df) <-
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16794
**[Test build #72321 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72321/testReport)**
for PR 16794 at commit
GitHub user dongjoon-hyun opened a pull request:
https://github.com/apache/spark/pull/16795
[WIP][SPARK-19409][BUILD] Fix ParquetAvroCompatibilitySuite failure due to
test dependency on avro
## What changes were proposed in this pull request?
After using Apache Parquet
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16793
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 project does not have this feature
Github user salilsurendran commented on a diff in the pull request:
https://github.com/apache/spark/pull/16664#discussion_r99415030
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/internal/SQLConf.scala ---
@@ -660,12 +660,21 @@ object SQLConf {
.booleanConf
Github user rxin commented on the issue:
https://github.com/apache/spark/pull/16792
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 and wishes so, or if the feature
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/16783
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 feature
enabled and wishes
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16791
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 does not have this feature
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16791
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/72315/
Test PASSed.
---
Github user dongjoon-hyun commented on the issue:
https://github.com/apache/spark/pull/12583
Hi, @bomeng , do you have something to refresh here?
I think we can close this for now.
---
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/16757#discussion_r99385357
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/optimizer/Optimizer.scala
---
@@ -154,56 +155,108 @@ class SimpleTestOptimizer
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16784
**[Test build #72312 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72312/testReport)**
for PR 16784 at commit
Github user dongjoon-hyun commented on the issue:
https://github.com/apache/spark/pull/16751
BTW, is there any condition to reproduce that? At least, `sbt` seems not to
complain like that.
```
$ build/sbt "project sql" "test-only *.ParquetAvroCompatibilitySuite"
...
Github user wangmiao1981 commented on the issue:
https://github.com/apache/spark/pull/16784
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 feature
enabled and
Github user gatorsmile commented on a diff in the pull request:
https://github.com/apache/spark/pull/16269#discussion_r99393281
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/plans/logical/basicLogicalOperators.scala
---
@@ -363,7 +363,8 @@ case class
Github user gatorsmile commented on a diff in the pull request:
https://github.com/apache/spark/pull/16269#discussion_r99394101
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/SparkStrategies.scala ---
@@ -405,32 +405,4 @@ abstract class SparkStrategies extends
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16784
**[Test build #72314 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72314/testReport)**
for PR 16784 at commit
Github user gatorsmile commented on a diff in the pull request:
https://github.com/apache/spark/pull/16269#discussion_r99394934
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/datasources/DataSourceStrategy.scala
---
@@ -273,10 +285,6 @@ object DataSourceStrategy
Github user gatorsmile commented on a diff in the pull request:
https://github.com/apache/spark/pull/16269#discussion_r99397097
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/datasources/ddl.scala ---
@@ -20,15 +20,23 @@ package
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16138
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 project does not have this feature
Github user dongjoon-hyun commented on the issue:
https://github.com/apache/spark/pull/16791
I see. Sure!
Right, it happens only maven build so far.
---
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 actuaryzhang commented on a diff in the pull request:
https://github.com/apache/spark/pull/16699#discussion_r99406022
--- Diff:
mllib/src/test/scala/org/apache/spark/ml/regression/GeneralizedLinearRegressionSuite.scala
---
@@ -743,6 +743,84 @@ class
Github user tcondie commented on a diff in the pull request:
https://github.com/apache/spark/pull/16686#discussion_r99381274
--- Diff:
external/kafka-0-10-sql/src/main/scala/org/apache/spark/sql/kafka010/KafkaOffsets.scala
---
@@ -19,14 +19,31 @@ package
Github user gatorsmile commented on a diff in the pull request:
https://github.com/apache/spark/pull/16269#discussion_r99397551
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/plans/logical/basicLogicalOperators.scala
---
@@ -374,25 +375,24 @@ case class
Github user hvanhovell commented on a diff in the pull request:
https://github.com/apache/spark/pull/16757#discussion_r99382442
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/optimizer/Optimizer.scala
---
@@ -154,56 +155,108 @@ class SimpleTestOptimizer
Github user wangmiao1981 commented on the issue:
https://github.com/apache/spark/pull/16784
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 have this feature
enabled
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16790
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 project does not have this
Github user igozali commented on the issue:
https://github.com/apache/spark/pull/16724
My original use case for sorting the output files based on timestamp using
Spark was to use the output files with some other machine learning framework
which might not readily work well with very
Github user gatorsmile commented on a diff in the pull request:
https://github.com/apache/spark/pull/16269#discussion_r99393848
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/SparkStrategies.scala ---
@@ -405,32 +405,4 @@ abstract class SparkStrategies extends
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16138
**[Test build #72311 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72311/testReport)**
for PR 16138 at commit
GitHub user liancheng opened a pull request:
https://github.com/apache/spark/pull/16791
[SPARK-19409][SPARK-17213] Cleanup Parquet workarounds/hacks due to bugs of
old Parquet versions
## What changes were proposed in this pull request?
We've already upgraded parquet-mr to
Github user dongjoon-hyun commented on the issue:
https://github.com/apache/spark/pull/16791
Originally, it's reported at #16751 by @robbinspg .
---
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 dongjoon-hyun commented on the issue:
https://github.com/apache/spark/pull/16791
I'll create another PR and ping 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 feature
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16787
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 project does not have this feature
GitHub user jinxing64 opened a pull request:
https://github.com/apache/spark/pull/16790
[SPARK-19450] Replace askWithRetry with askSync.
## What changes were proposed in this pull request?
`askSync` is already added in `RpcEndpointRef` (see SPARK-19347 and
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16787
**[Test build #72309 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72309/testReport)**
for PR 16787 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15770
**[Test build #72313 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72313/testReport)**
for PR 15770 at commit
Github user gatorsmile commented on a diff in the pull request:
https://github.com/apache/spark/pull/16269#discussion_r99398131
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/datasources/ddl.scala ---
@@ -20,15 +20,23 @@ package
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15770
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 does not have this feature
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15770
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/72313/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16138
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/72311/
Test FAILed.
---
Github user dongjoon-hyun commented on the issue:
https://github.com/apache/spark/pull/16791
Yep. The failure is on #16751 . It's my bad.
---
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 gatorsmile commented on a diff in the pull request:
https://github.com/apache/spark/pull/16269#discussion_r99391020
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/analysis/CheckAnalysis.scala
---
@@ -413,6 +391,10 @@ trait CheckAnalysis extends
Github user gatorsmile commented on a diff in the pull request:
https://github.com/apache/spark/pull/16269#discussion_r99391911
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/analysis/CheckAnalysis.scala
---
@@ -376,28 +376,6 @@ trait CheckAnalysis extends
1 - 100 of 507 matches
Mail list logo
