Github user gatorsmile commented on a diff in the pull request:
https://github.com/apache/spark/pull/17581#discussion_r111069701
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/internal/SQLConf.scala ---
@@ -359,6 +359,16 @@ object SQLConf {
.booleanConf
Github user gatorsmile commented on a diff in the pull request:
https://github.com/apache/spark/pull/17581#discussion_r111069617
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/internal/SQLConf.scala ---
@@ -359,6 +359,16 @@ object SQLConf {
.booleanConf
Github user wangmiao1981 commented on the issue:
https://github.com/apache/spark/pull/17611
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 wangmiao1981 commented on the issue:
https://github.com/apache/spark/pull/17611
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 this feature
enabled
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17524
**[Test build #75727 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/75727/testReport)**
for PR 17524 at commit
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/17524
ok to test
---
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
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17613
**[Test build #75726 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/75726/testReport)**
for PR 17613 at commit
Github user gatorsmile commented on a diff in the pull request:
https://github.com/apache/spark/pull/17615#discussion_r111068193
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/command/functions.scala
---
@@ -59,17 +60,13 @@ case class CreateFunctionCommand(
Github user gatorsmile commented on a diff in the pull request:
https://github.com/apache/spark/pull/17615#discussion_r111068131
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/catalog/SessionCatalog.scala
---
@@ -1050,7 +1050,7 @@ class SessionCatalog(
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17615
**[Test build #75725 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/75725/testReport)**
for PR 17615 at commit
Github user gatorsmile commented on a diff in the pull request:
https://github.com/apache/spark/pull/17615#discussion_r111068037
--- Diff:
sql/hive/src/main/scala/org/apache/spark/sql/hive/HiveSessionCatalog.scala ---
@@ -124,13 +124,6 @@ private[sql] class HiveSessionCatalog(
Github user brkyvz commented on a diff in the pull request:
https://github.com/apache/spark/pull/17613#discussion_r111067826
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/streaming/StreamExecution.scala
---
@@ -284,42 +284,38 @@ class StreamExecution(
GitHub user gatorsmile opened a pull request:
https://github.com/apache/spark/pull/17615
[SPARK-20303][SQL] Rename createTempFunction to registerFunction
### What changes were proposed in this pull request?
Session catalog API `createTempFunction` is being used by Hive build-in
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17613
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/75720/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17613
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/17613
**[Test build #75720 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/75720/testReport)**
for PR 17613 at commit
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/17614#discussion_r111064001
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/types/DataType.scala ---
@@ -288,4 +288,30 @@ object DataType {
case (fromDataType,
Github user ioana-delaney commented on a diff in the pull request:
https://github.com/apache/spark/pull/17546#discussion_r111063912
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/optimizer/CostBasedJoinReorder.scala
---
@@ -54,8 +54,6 @@ case class
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17614
**[Test build #75724 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/75724/testReport)**
for PR 17614 at commit
Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/17614#discussion_r111063773
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/types/DataType.scala ---
@@ -288,4 +288,30 @@ object DataType {
case (fromDataType,
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/17590
I think it is because it only checks multiple dots and the case I described
above was finally found now (in my previous PR related with `from_json`
function).
I think multiple dots are
Github user zenglinxi0615 closed the pull request at:
https://github.com/apache/spark/pull/17550
---
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 zenglinxi0615 commented on the issue:
https://github.com/apache/spark/pull/17550
okï¼going to close this PR and open a new PR using the master branch.
---
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 issue:
https://github.com/apache/spark/pull/17586
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 dilipbiswal commented on the issue:
https://github.com/apache/spark/pull/17330
@cloud-fan Thanks a lot!!
---
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/17586
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/75721/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17586
**[Test build #75721 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/75721/testReport)**
for PR 17586 at commit
Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/17436#discussion_r111062746
--- Diff:
core/src/main/scala/org/apache/spark/memory/UnifiedMemoryManager.scala ---
@@ -210,7 +210,7 @@ object UnifiedMemoryManager {
private def
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/17330
---
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 cloud-fan commented on the issue:
https://github.com/apache/spark/pull/17330
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 felixcheung commented on the issue:
https://github.com/apache/spark/pull/17590
Changes look fine. I think we should get some feedback on style/guideline
changes like this though.
Also do you know why we don't ever see these types of error in Jenkins? Is
it
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17469
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/17469
**[Test build #75723 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/75723/testReport)**
for PR 17469 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17469
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/75723/
Test FAILed.
---
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/17375
@joshrosen, do you mind if I ask a quick look here? I know you know PySpark
well. I think this backport got a sign-off and a positive comment from both
committers.
---
If your project is set
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/17477
Looks there is another break.
```
[error]
/home/jenkins/workspace/SparkPullRequestBuilder/sql/core/target/java/org/apache/spark/sql/catalog/Catalog.java:453:
error: reference not
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17477
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/75722/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17477
**[Test build #75722 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/75722/testReport)**
for PR 17477 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17477
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/17469
**[Test build #75723 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/75723/testReport)**
for PR 17469 at commit
Github user JoshRosen commented on the issue:
https://github.com/apache/spark/pull/17469
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 and
Github user JoshRosen commented on the issue:
https://github.com/apache/spark/pull/17477
Let a few nitpicky comments.
@srowen @jkbradley, could you take a look and merge it after changes if it
looks okay to you? Overall build change structure looks okay to me if we're
fine
Github user JoshRosen commented on a diff in the pull request:
https://github.com/apache/spark/pull/17477#discussion_r111059960
--- Diff:
mllib/src/main/scala/org/apache/spark/ml/classification/Classifier.scala ---
@@ -74,7 +74,7 @@ abstract class Classifier[
*
Github user JoshRosen commented on a diff in the pull request:
https://github.com/apache/spark/pull/17477#discussion_r111059991
--- Diff:
mllib/src/main/scala/org/apache/spark/ml/classification/Classifier.scala ---
@@ -74,7 +74,7 @@ abstract class Classifier[
*
Github user JoshRosen commented on a diff in the pull request:
https://github.com/apache/spark/pull/17477#discussion_r111059834
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/TaskSchedulerImpl.scala ---
@@ -704,12 +704,12 @@ private[spark] object TaskSchedulerImpl {
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17477
**[Test build #75722 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/75722/testReport)**
for PR 17477 at commit
Github user JoshRosen commented on a diff in the pull request:
https://github.com/apache/spark/pull/17477#discussion_r111059727
--- Diff: core/src/main/scala/org/apache/spark/rpc/RpcEndpoint.scala ---
@@ -33,9 +33,9 @@ private[spark] trait RpcEnvFactory {
*
* It is
Github user yssharma commented on the issue:
https://github.com/apache/spark/pull/17467
Waiting for review @brkyvz . 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 have this feature
Github user JoshRosen commented on the issue:
https://github.com/apache/spark/pull/17477
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 and
Github user yssharma commented on the issue:
https://github.com/apache/spark/pull/17506
@srowen do you feel this patch could be merged now ?
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
Github user dongjoon-hyun commented on the issue:
https://github.com/apache/spark/pull/17612
Oh, thank you, @gatorsmile !
---
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 tdas commented on a diff in the pull request:
https://github.com/apache/spark/pull/17613#discussion_r111058990
--- Diff:
sql/core/src/test/scala/org/apache/spark/sql/streaming/StreamTest.scala ---
@@ -277,6 +277,11 @@ trait StreamTest extends QueryTest with
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17586
**[Test build #75721 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/75721/testReport)**
for PR 17586 at commit
Github user tdas commented on a diff in the pull request:
https://github.com/apache/spark/pull/17613#discussion_r111058917
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/streaming/StreamExecution.scala
---
@@ -284,42 +284,38 @@ class StreamExecution(
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/17606
---
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 cloud-fan commented on the issue:
https://github.com/apache/spark/pull/17606
LGTM, merging to master!
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and
Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/17546#discussion_r111058094
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/optimizer/CostBasedJoinReorder.scala
---
@@ -54,8 +54,6 @@ case class
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17613
**[Test build #75720 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/75720/testReport)**
for PR 17613 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17222
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/75719/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17222
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 brkyvz opened a pull request:
https://github.com/apache/spark/pull/17613
[SPARK-20301][FLAKY-TEST][DO NOT MERGE] Fix Hadoop Shell.runCommand
flakiness in Structured Streaming tests
## What changes were proposed in this pull request?
Some Structured Streaming
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17222
**[Test build #75719 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/75719/testReport)**
for PR 17222 at commit
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/17612
---
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 gatorsmile commented on the issue:
https://github.com/apache/spark/pull/17612
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 guoxiaolongzte commented on the issue:
https://github.com/apache/spark/pull/17608
I just downloaded the latest spark master code to compile and install ,
test the problem, there are still bugs, the page is wrong.
---
If your project is set up for it, you can reply to
Github user ashokblend commented on the issue:
https://github.com/apache/spark/pull/16057
Any Reason why its not merged in branch2.1
---
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 ashokblend commented on the issue:
https://github.com/apache/spark/pull/16057
Hi Guys
---
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
Github user guoxiaolongzte commented on the issue:
https://github.com/apache/spark/pull/17608
So how do I deal with this PR?@ajbozarth
---
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 ajbozarth commented on the issue:
https://github.com/apache/spark/pull/17608
On a quick git blame this is my code that seems to be broken. I'll take a
more detailed look when I can in the next couple days.
---
If your project is set up for it, you can reply to this email
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16774
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/75716/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16774
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/16774
**[Test build #75716 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/75716/testReport)**
for PR 16774 at commit
Github user tnachen commented on the issue:
https://github.com/apache/spark/pull/17109
@srowen Appreciate the help you're doing, I think we're doing what we can
to help review these patches and making sure Mesos support is still being
maintained and improved over time.
If you
Github user ajbozarth commented on the issue:
https://github.com/apache/spark/pull/17608
After taking another look I was mixing this bug up with another when I
asked that
---
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 guoxiaolongzte commented on the issue:
https://github.com/apache/spark/pull/17608
@ajbozarth I am using the latest spark version.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17612
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/75717/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17222
**[Test build #75719 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/75719/testReport)**
for PR 17222 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17612
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/17612
**[Test build #75717 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/75717/testReport)**
for PR 17612 at commit
Github user zjffdu commented on the issue:
https://github.com/apache/spark/pull/17222
Good catch ! @holdenk `return` is removed.
---
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/17586
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/17586
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/75718/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17586
**[Test build #75718 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/75718/testReport)**
for PR 17586 at commit
Github user skonto commented on a diff in the pull request:
https://github.com/apache/spark/pull/17109#discussion_r111045370
--- Diff:
resource-managers/mesos/src/main/scala/org/apache/spark/scheduler/cluster/mesos/MesosSchedulerBackendUtil.scala
---
@@ -99,6 +99,26 @@
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/17469
@map222, thanks, I don't have a permission to retrigger the build and know
why it does not automatically from the newly pushed commit. Would be great if
@srowen or @holdenk are able to
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17586
**[Test build #75718 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/75718/testReport)**
for PR 17586 at commit
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/17469
@map222, thanks, I don't have a permission to retrigger the build and know
why it does not. Would be great if @srowen or @holdenk are able to retrigger
the build.
---
If your project is set
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/17477
@joshrosen, I am fine with closing it for now if you are currently not sure
of it.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17612
**[Test build #75717 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/75717/testReport)**
for PR 17612 at commit
Github user dongjoon-hyun commented on the issue:
https://github.com/apache/spark/pull/17612
Hi, @gatorsmile .
If possible, can we update the docs consistently with the code, too?
---
If your project is set up for it, you can reply to this email and have your
reply appear on
GitHub user dongjoon-hyun opened a pull request:
https://github.com/apache/spark/pull/17612
[MINOR][DOCS] Update supported versions for Hive Metastore
## What changes were proposed in this pull request?
Since SPARK-18112 and SPARK-13446, Apache Spark starts to support
Github user BryanCutler commented on a diff in the pull request:
https://github.com/apache/spark/pull/16774#discussion_r111042302
--- Diff:
examples/src/main/scala/org/apache/spark/examples/ml/ModelSelectionViaTrainValidationSplitExample.scala
---
@@ -65,6 +65,8 @@ object
Github user zjffdu commented on a diff in the pull request:
https://github.com/apache/spark/pull/17586#discussion_r111042227
--- Diff:
mllib/src/main/scala/org/apache/spark/ml/classification/LinearSVC.scala ---
@@ -355,6 +368,19 @@ object LinearSVCModel extends
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16774
**[Test build #75716 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/75716/testReport)**
for PR 16774 at commit
Github user BryanCutler commented on the issue:
https://github.com/apache/spark/pull/16774
Thanks for the review @MLnick! I changed `setExecutorService` to use a
trait instead of just a function, which can be implemented in Java. Works the
same, but does add the public trait if
Github user zjffdu commented on a diff in the pull request:
https://github.com/apache/spark/pull/17586#discussion_r111042049
--- Diff:
mllib/src/main/scala/org/apache/spark/ml/classification/LinearSVC.scala ---
@@ -355,6 +368,19 @@ object LinearSVCModel extends
Github user mridulm commented on the issue:
https://github.com/apache/spark/pull/17610
bq. I don't get it. But I think the stack trace shows why this dead-lock
happens.
Based on your description/stacktrace, I get why the deadlock happens - what
I meant was, do any of the super.*
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/17527
Do you mind if I ask a example case? I just would like to look into this to
help.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/17527
Thank you for your explanation. Just did a few run in our DDL support. We
still have a few bugs in the locale support. If we use Turkish locale, a few
test cases failed.
Do you know
Github user zjffdu commented on the issue:
https://github.com/apache/spark/pull/16906
Kindly ping @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
1 - 100 of 363 matches
Mail list logo
