Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17014
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/17014
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/73214/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17014
**[Test build #73214 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/73214/testReport)**
for PR 17014 at commit
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/17013
Thanks for your review @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 AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17013
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/73210/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17013
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/17015
**[Test build #73212 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/73212/testReport)**
for PR 17015 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16971
**[Test build #73211 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/73211/testReport)**
for PR 16971 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17015
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/73212/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17015
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/16971
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/73211/
Test PASSed.
---
GitHub user zhengruifeng opened a pull request:
https://github.com/apache/spark/pull/17016
[SPARK-19679][ML] Destroy broadcasted object without blocking
## What changes were proposed in this pull request?
Destroy broadcasted object without blocking
use `find mllib -name
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16977
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 opened a pull request:
https://github.com/apache/spark/pull/17013
[SPARK-19666][SQL] Improve error message for JavaBean without getter
## What changes were proposed in this pull request?
Currently, if we use a JavaBean without the getter as below:
Github user maropu commented on a diff in the pull request:
https://github.com/apache/spark/pull/17013#discussion_r102175210
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/JavaTypeInference.scala
---
@@ -123,7 +123,11 @@ object JavaTypeInference {
Github user HyukjinKwon commented on a diff in the pull request:
https://github.com/apache/spark/pull/17013#discussion_r102177949
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/JavaTypeInference.scala
---
@@ -123,7 +123,11 @@ object JavaTypeInference {
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17011
**[Test build #73218 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/73218/testReport)**
for PR 17011 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17014
**[Test build #73217 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/73217/testReport)**
for PR 17014 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16971
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/17014
**[Test build #73209 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/73209/testReport)**
for PR 17014 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17014
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/73209/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17014
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/17015
**[Test build #73212 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/73212/testReport)**
for PR 17015 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17014
**[Test build #73215 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/73215/testReport)**
for PR 17014 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17013
**[Test build #73210 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/73210/testReport)**
for PR 17013 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17011
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/17011
**[Test build #73206 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/73206/testReport)**
for PR 17011 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17011
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/73206/
Test FAILed.
---
GitHub user zhengruifeng opened a pull request:
https://github.com/apache/spark/pull/17014
[SPARK-18608][ML][WIP] Fix double-caching in ML algorithms
## What changes were proposed in this pull request?
1, For Predictors, use `train(dataset: Dataset[_], handlePersistence:
Github user zhengruifeng commented on a diff in the pull request:
https://github.com/apache/spark/pull/16971#discussion_r102167055
--- Diff:
sql/core/src/test/scala/org/apache/spark/sql/DataFrameStatSuite.scala ---
@@ -214,20 +214,29 @@ class DataFrameStatSuite extends QueryTest
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17014
**[Test build #73214 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/73214/testReport)**
for PR 17014 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16990
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/16990
**[Test build #73207 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/73207/testReport)**
for PR 16990 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16990
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/73207/
Test PASSed.
---
Github user HyukjinKwon commented on a diff in the pull request:
https://github.com/apache/spark/pull/17013#discussion_r102164904
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/JavaTypeInference.scala
---
@@ -123,7 +123,11 @@ object JavaTypeInference {
Github user maropu commented on a diff in the pull request:
https://github.com/apache/spark/pull/17013#discussion_r102175873
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/JavaTypeInference.scala
---
@@ -123,7 +123,11 @@ object JavaTypeInference {
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17016
**[Test build #73220 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/73220/testReport)**
for PR 17016 at commit
Github user felixcheung commented on the issue:
https://github.com/apache/spark/pull/16976
I see, fair enough. cc @falaki
---
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 felixcheung commented on a diff in the pull request:
https://github.com/apache/spark/pull/15125#discussion_r102168380
--- Diff: docs/graphx-programming-guide.md ---
@@ -708,7 +708,9 @@ messages remaining.
> messaging function. These constraints allow additional
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17014
**[Test build #73217 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/73217/testReport)**
for PR 17014 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17014
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/73217/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17014
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/16977
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/73208/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16977
**[Test build #73208 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/73208/testReport)**
for PR 16977 at commit
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/17013
It seems ideally we should filter all out assuming from
> // TODO: we should only collect properties that have getter and setter.
However, some tests
> // pass in scala case class
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/16997
Could you fix the PR title too while you are online maybe? It might be nice
to have a good title for both a commit log and those who like to track down the
history.
---
If your project is set
GitHub user cloud-fan opened a pull request:
https://github.com/apache/spark/pull/17015
[SPARK-19678][SQL] remove MetastoreRelation
## What changes were proposed in this pull request?
`MetastoreRelation` is used to represent table relation for hive tables,
and provides
Github user cloud-fan commented on the issue:
https://github.com/apache/spark/pull/17015
cc @gatorsmile @sameeragarwal
---
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 SparkQA commented on the issue:
https://github.com/apache/spark/pull/17013
**[Test build #73210 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/73210/testReport)**
for PR 17013 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17014
**[Test build #73209 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/73209/testReport)**
for PR 17014 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16971
**[Test build #73211 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/73211/testReport)**
for PR 16971 at commit
Github user HarshSharma8 commented on the issue:
https://github.com/apache/spark/pull/16997
I updated the content with a demo object. I would appreciate if anyone can
have 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 user HarshSharma8 commented on the issue:
https://github.com/apache/spark/pull/16997
Hello HyukjinKwon,
I have updated the title, i wish you like it, it shows what is there in the
content. And commit has already been made.
---
If your project is set up for it, you can
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17014
**[Test build #73213 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/73213/testReport)**
for PR 17014 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17013
**[Test build #73216 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/73216/testReport)**
for PR 17013 at commit
Github user uncleGen commented on the issue:
https://github.com/apache/spark/pull/17011
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 HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/17013
cc @cloud-fan who I saw in the related PR while tracking down the history.
---
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 SparkQA commented on the issue:
https://github.com/apache/spark/pull/17014
**[Test build #73213 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/73213/testReport)**
for PR 17014 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17014
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/17014
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/73213/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17014
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/17014
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/73215/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17014
**[Test build #73215 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/73215/testReport)**
for PR 17014 at commit
Github user HyukjinKwon commented on a diff in the pull request:
https://github.com/apache/spark/pull/17013#discussion_r102182533
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/JavaTypeInference.scala
---
@@ -123,7 +123,11 @@ object JavaTypeInference {
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17014
**[Test build #73219 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/73219/testReport)**
for PR 17014 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17014
**[Test build #73219 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/73219/testReport)**
for PR 17014 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17014
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/73219/
Test FAILed.
---
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/17013#discussion_r102202049
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/JavaTypeInference.scala
---
@@ -123,7 +123,11 @@ object JavaTypeInference {
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17013
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/73216/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17013
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/17013
**[Test build #73216 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/73216/testReport)**
for PR 17013 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17011
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/73218/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17011
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/17011
**[Test build #73218 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/73218/testReport)**
for PR 17011 at commit
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/17011
I don't quite see why it can succeed in listing a file that's not readable,
later in mergeApplicationListing? won't that fail or generate an error already?
Therefore I'm wondering if this is really
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17014
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 vanzin opened a pull request:
https://github.com/apache/spark/pull/17019
[SPARK-19652][UI] Do auth checks for REST API access (branch-2.1).
The REST API has a security filter that performs auth checks
based on the UI root's security manager. That works fine when
Github user vanzin commented on the issue:
https://github.com/apache/spark/pull/17019
There as a conflict in the MimaExcludes list, just checking that I didn't
break it.
---
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 brkyvz commented on a diff in the pull request:
https://github.com/apache/spark/pull/16744#discussion_r102355832
--- Diff: python/pyspark/streaming/kinesis.py ---
@@ -67,6 +68,12 @@ def createStream(ssc, kinesisAppName, streamName,
endpointUrl, regionName,
Github user sameeragarwal commented on the issue:
https://github.com/apache/spark/pull/16998
@viirya please correct me if I'm wrong but scanning through this patch, it
appears that the underlying problem is that duplicating and tracking aliased
constraints using a `Set` tends to blow
Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/16928#discussion_r102363460
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/datasources/csv/CSVFileFormat.scala
---
@@ -96,31 +96,44 @@ class CSVFileFormat extends
Github user wesm commented on the issue:
https://github.com/apache/spark/pull/15821
The 0.2 Maven artifacts have been posted. I'll try to update the
conda-forge packages this week -- if anyone can help with conda-forge
maintenance that would be a big help.
Thanks!
---
If
Github user maropu commented on a diff in the pull request:
https://github.com/apache/spark/pull/16928#discussion_r102367846
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/datasources/csv/UnivocityParser.scala
---
@@ -147,8 +165,6 @@ private[csv] class
Github user uncleGen closed the pull request at:
https://github.com/apache/spark/pull/17011
---
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/16928
**[Test build #73250 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/73250/testReport)**
for PR 16928 at commit
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/17004
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 tdas commented on the issue:
https://github.com/apache/spark/pull/16979
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
GitHub user zhengruifeng opened a pull request:
https://github.com/apache/spark/pull/17021
[SPARK-19694][ML] Add missing 'setTopicDistributionCol' for LDAModel
## What changes were proposed in this pull request?
Add missing 'setTopicDistributionCol' for LDAModel
## How was
Github user tdas commented on a diff in the pull request:
https://github.com/apache/spark/pull/16970#discussion_r102380326
--- Diff:
sql/core/src/test/scala/org/apache/spark/sql/streaming/DeduplicationSuite.scala
---
@@ -0,0 +1,252 @@
+/*
+ * Licensed to the Apache
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17013
**[Test build #73258 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/73258/testReport)**
for PR 17013 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17022
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 zsxwing closed the pull request at:
https://github.com/apache/spark/pull/16979
---
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/16928
**[Test build #73251 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/73251/testReport)**
for PR 16928 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17021
**[Test build #73255 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/73255/testReport)**
for PR 17021 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17021
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 HyukjinKwon commented on a diff in the pull request:
https://github.com/apache/spark/pull/17013#discussion_r102352788
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/JavaTypeInference.scala
---
@@ -123,7 +123,11 @@ object JavaTypeInference {
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16744
**[Test build #73244 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/73244/testReport)**
for PR 16744 at commit
Github user jerryshao commented on a diff in the pull request:
https://github.com/apache/spark/pull/16923#discussion_r102357394
--- Diff:
sql/hive/src/main/scala/org/apache/spark/sql/hive/client/HiveClientImpl.scala
---
@@ -106,21 +106,27 @@ private[hive] class HiveClientImpl(
Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/17015#discussion_r102360866
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/catalog/interface.scala
---
@@ -349,36 +350,42 @@ object CatalogTypes {
Github user cloud-fan commented on the issue:
https://github.com/apache/spark/pull/17015
I don't think `UnresolvedCatalogRelation` is necessary. Data source table
can treat `CatalogRelation` as unresolved but it's its own business. When we
replace `CatalogRelation` to
1 - 100 of 531 matches
Mail list logo
