Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18373
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/78354/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18373
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 devaraj-kavali commented on the issue:
https://github.com/apache/spark/pull/18357
> But can you double check that this change won't terminate a
still-functional worker?
The change doesn't impact/harm the fully functional Worker,
SparkUncaughtExceptionHandler
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18373
**[Test build #78354 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/78354/testReport)**
for PR 18373 at commit
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/18106
https://www.ibm.com/support/knowledgecenter/en/SSEPGG_9.7.0/com.ibm.db2.luw.sql.ref.doc/doc/r863.html
I might not have the bandwidth to review this PR until this weekend.
@viirya
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17758
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/17758
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/78353/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17758
**[Test build #78353 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/78353/testReport)**
for PR 17758 at commit
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/9162
---
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 wangyum commented on the issue:
https://github.com/apache/spark/pull/18106
Yes, I also tend to be one `trunc` function. I found Presto provides two
functions `date_trunc` and `truncate`.
---
If your project is set up for it, you can reply to this email and have your
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/9162
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 have this feature
enabled and
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18356
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/18356
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/78357/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18356
**[Test build #78357 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/78357/testReport)**
for PR 18356 at commit
Github user gatorsmile commented on a diff in the pull request:
https://github.com/apache/spark/pull/18356#discussion_r123157059
--- Diff:
sql/core/src/test/scala/org/apache/spark/sql/test/DataFrameReaderWriterSuite.scala
---
@@ -678,4 +679,34 @@ class DataFrameReaderWriterSuite
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/9162
The scope of this PR is just to the DB2 dialect. The risk is pretty small
even if the fix might not cover all the scenarios. Thanks! @sureshthalamati
LGTM
---
If your project is set up
Github user viirya commented on the issue:
https://github.com/apache/spark/pull/18106
Although then we can't use just one `trunc` function, it seems ok for me
because not all databases use `trunc` to truncate both number and datetime.
---
If your project is set up for it, you can
Github user gatorsmile commented on a diff in the pull request:
https://github.com/apache/spark/pull/18356#discussion_r123156355
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/datasources/DataSource.scala
---
@@ -181,6 +197,12 @@ case class DataSource(
Github user taroplus commented on the issue:
https://github.com/apache/spark/pull/17074
SPARK-18646 is the one I filed, SPARK-19675 is the one I filed. But it kept
getting closed again and again, so I linked my PR to SPARK-18646 which is still
open.
But I think I know what
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17074
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/78368/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17074
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/17074
**[Test build #78368 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/78368/testReport)**
for PR 17074 at commit
Github user viirya commented on the issue:
https://github.com/apache/spark/pull/18106
Is there duplicated codes between trunc(number) and trunc(date)? If no,
seems to me we don't necessarily let one expression to have two different
features.
---
If your project is set up for it,
Github user viirya commented on a diff in the pull request:
https://github.com/apache/spark/pull/18106#discussion_r123155483
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/misc.scala
---
@@ -132,3 +133,141 @@ case class Uuid() extends
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17074
**[Test build #78368 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/78368/testReport)**
for PR 17074 at commit
Github user taroplus commented on a diff in the pull request:
https://github.com/apache/spark/pull/17074#discussion_r123154753
--- Diff:
repl/src/main/scala/org/apache/spark/repl/ExecutorClassLoader.scala ---
@@ -44,7 +44,7 @@ class ExecutorClassLoader(
env: SparkEnv,
Github user taroplus commented on a diff in the pull request:
https://github.com/apache/spark/pull/17074#discussion_r123153668
--- Diff:
repl/src/test/scala/org/apache/spark/repl/ExecutorClassLoaderSuite.scala ---
@@ -77,6 +79,50 @@ class ExecutorClassLoaderSuite
}
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/18373
Thanks for triggering tests and fixing Jenkins @shaneknapp.
---
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 assafmendelson closed the pull request at:
https://github.com/apache/spark/pull/18363
---
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
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/18373
I skimmed `SparkSession`, `Dataset` and `functions.scala`. I think I can
add it ,in `SparkSession` , to
```
def createDataFrame(rowRDD: RDD[Row], schema: StructType)
def
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18355
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/78358/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18355
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 SparkQA commented on the issue:
https://github.com/apache/spark/pull/18355
**[Test build #78358 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/78358/testReport)**
for PR 18355 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18373
**[Test build #78367 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/78367/testReport)**
for PR 18373 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18092
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/78366/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18092
**[Test build #78366 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/78366/testReport)**
for PR 18092 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18092
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 SparkQA commented on the issue:
https://github.com/apache/spark/pull/18092
**[Test build #78366 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/78366/testReport)**
for PR 18092 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18092
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 SparkQA commented on the issue:
https://github.com/apache/spark/pull/18092
**[Test build #78365 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/78365/testReport)**
for PR 18092 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18092
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/78365/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18092
**[Test build #78365 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/78365/testReport)**
for PR 18092 at commit
Github user kiszk commented on the issue:
https://github.com/apache/spark/pull/15227
Could you please add the simple generated code in the description before
and after applying this PR?
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17471
**[Test build #78363 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/78363/testReport)**
for PR 17471 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18309
**[Test build #78359 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/78359/testReport)**
for PR 18309 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15417
**[Test build #78364 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/78364/testReport)**
for PR 15417 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18106
**[Test build #78362 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/78362/testReport)**
for PR 18106 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18373
**[Test build #78354 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/78354/testReport)**
for PR 18373 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18355
**[Test build #78358 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/78358/testReport)**
for PR 18355 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18356
**[Test build #78357 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/78357/testReport)**
for PR 18356 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18293
**[Test build #78360 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/78360/testReport)**
for PR 18293 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18233
**[Test build #78361 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/78361/testReport)**
for PR 18233 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18367
**[Test build #78355 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/78355/testReport)**
for PR 18367 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18365
**[Test build #78356 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/78356/testReport)**
for PR 18365 at commit
Github user shaneknapp commented on the issue:
https://github.com/apache/spark/pull/18367
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 feature
enabled and wishes so,
Github user shaneknapp commented on the issue:
https://github.com/apache/spark/pull/18309
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 feature
enabled and wishes so,
Github user shaneknapp commented on the issue:
https://github.com/apache/spark/pull/18106
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 feature
enabled and wishes so,
Github user shaneknapp commented on the issue:
https://github.com/apache/spark/pull/18356
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 feature
enabled and wishes so,
Github user shaneknapp commented on the issue:
https://github.com/apache/spark/pull/18293
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 feature
enabled and wishes so,
Github user shaneknapp commented on the issue:
https://github.com/apache/spark/pull/17471
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 feature
enabled and wishes so,
Github user shaneknapp commented on the issue:
https://github.com/apache/spark/pull/18355
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 feature
enabled and wishes so,
Github user shaneknapp commented on the issue:
https://github.com/apache/spark/pull/18233
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 feature
enabled and wishes so,
Github user shaneknapp commented on the issue:
https://github.com/apache/spark/pull/15417
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 feature
enabled and wishes so,
Github user shaneknapp commented on the issue:
https://github.com/apache/spark/pull/18373
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 feature
enabled and wishes so,
Github user shaneknapp commented on the issue:
https://github.com/apache/spark/pull/18365
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 feature
enabled and wishes so,
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17758
**[Test build #78353 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/78353/testReport)**
for PR 17758 at commit
Github user maropu commented on the issue:
https://github.com/apache/spark/pull/18373
Thanks for follow-up! IMHO this syntax helps much, so we could support this
in other cases for defining schemas (e.g., `spark.createDataFrame`)? (I think
it's impossible to support in all the cases
Github user maropu commented on a diff in the pull request:
https://github.com/apache/spark/pull/18373#discussion_r123150122
--- Diff:
sql/core/src/test/scala/org/apache/spark/sql/streaming/test/DataStreamReaderWriterSuite.scala
---
@@ -663,4 +663,16 @@ class
Github user jiangxb1987 commented on the issue:
https://github.com/apache/spark/pull/17074
In the jira, you mentioned `ExecutorClassLoader.getParent()` will return
the unexpected class loader, could you explain where we call this? At least I
didn't see them in Spark codebase.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18332
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/78340/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18332
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/18332
**[Test build #78340 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/78340/testReport)**
for PR 18332 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/9162
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/78337/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/9162
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/9162
**[Test build #78337 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/78337/testReport)**
for PR 9162 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18373
**[Test build #78352 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/78352/testReport)**
for PR 18373 at commit
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/18373
cc @gatorsmile, @zsxwing and @maropu.
---
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 HyukjinKwon opened a pull request:
https://github.com/apache/spark/pull/18373
[SPARK-20431][FOLLOWUP][SS] Specify a schema by using a DDL-formatted
string in DataStreamReader
## What changes were proposed in this pull request?
This pr supported a DDL-formatted
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18309
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/18309
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/78343/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18309
**[Test build #78343 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/78343/testReport)**
for PR 18309 at commit
Github user viirya commented on a diff in the pull request:
https://github.com/apache/spark/pull/18301#discussion_r123142588
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/metric/SQLMetrics.scala
---
@@ -74,6 +80,19 @@ object SQLMetrics {
private val
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17113
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/78334/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17113
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 SparkQA commented on the issue:
https://github.com/apache/spark/pull/17113
**[Test build #78334 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/78334/testReport)**
for PR 17113 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15417
**[Test build #78351 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/78351/testReport)**
for PR 15417 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18365
**[Test build #78350 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/78350/testReport)**
for PR 18365 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18355
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/18355
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/78349/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18355
**[Test build #78349 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/78349/testReport)**
for PR 18355 at commit
Github user viirya commented on the issue:
https://github.com/apache/spark/pull/18346
Another concern I might have is that `CodegenFallback` is already exposed
to users. So is it ok to remove it now?
---
If your project is set up for it, you can reply to this email and have your
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/18320
I checked R tests and the reproducer in the PR description passed fine on
CentOS.
> The other thing that would be good to manually test (since its not easy
to write a unit test) is to
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18356
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 HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/18320
I checked R tests and the reproducer in the PR description passed fine.
> The other thing that would be good to manually test (since its not easy
to write a unit test) is to see if the
Github user cloud-fan commented on the issue:
https://github.com/apache/spark/pull/18357
according to the JIRA, if the worker meets some unrecoverable issues and
the state becomes DEAD, it seems make sense to terminate this worker as it's
not functional. But can you double check that
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18356
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/78345/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18356
**[Test build #78345 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/78345/testReport)**
for PR 18356 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18355
**[Test build #78349 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/78349/testReport)**
for PR 18355 at commit
Github user maropu commented on a diff in the pull request:
https://github.com/apache/spark/pull/18300#discussion_r123138515
--- Diff: sql/core/src/test/scala/org/apache/spark/sql/DataFrameSuite.scala
---
@@ -112,6 +112,52 @@ class DataFrameSuite extends QueryTest with
Github user maropu commented on the issue:
https://github.com/apache/spark/pull/18356
@gatorsmile Is the test is valid?
https://github.com/apache/spark/blob/master/sql/hive/src/test/scala/org/apache/spark/sql/sources/ParquetHadoopFsRelationSuite.scala#L45
This test fails when this pr
1 - 100 of 607 matches
Mail list logo
