Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18587
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/79462/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18587
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/18587
**[Test build #79462 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/79462/testReport)**
for PR 18587 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18586
**[Test build #3841 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3841/testReport)**
for PR 18586 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18581
**[Test build #79465 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/79465/testReport)**
for PR 18581 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18498
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/79461/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18498
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/18555
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/18498
**[Test build #79461 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/79461/testReport)**
for PR 18498 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18555
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/79460/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18555
**[Test build #79460 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/79460/testReport)**
for PR 18555 at commit
Github user chie8842 commented on the issue:
https://github.com/apache/spark/pull/18586
@srowen Thank you for pointing out about test fail. I fixed it.
---
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 AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18584
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/79459/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18584
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/18584
**[Test build #79459 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/79459/testReport)**
for PR 18584 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18589
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/18589
**[Test build #79464 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/79464/testReport)**
for PR 18589 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18589
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/79464/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18589
**[Test build #79464 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/79464/testReport)**
for PR 18589 at commit
GitHub user zhengruifeng opened a pull request:
https://github.com/apache/spark/pull/18589
[SPARK-16872][ML] Add Gaussian NB
## What changes were proposed in this pull request?
Add Gaussian NB
## How was this patch tested?
existing tests and added tests
You can
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18583
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/18583
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/79458/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18583
**[Test build #79458 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/79458/testReport)**
for PR 18583 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18576
**[Test build #79463 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/79463/testReport)**
for PR 18576 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18300
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/18300
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/79457/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18300
**[Test build #79457 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/79457/testReport)**
for PR 18300 at commit
Github user maropu commented on the issue:
https://github.com/apache/spark/pull/18576
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 maropu commented on the issue:
https://github.com/apache/spark/pull/18581
yea, thanks for pinging me! I'll check and comment on it later.
---
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 Softsapiens closed the pull request at:
https://github.com/apache/spark/pull/18588
---
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 Softsapiens opened a pull request:
https://github.com/apache/spark/pull/18588
Branch 2.0
## What changes were proposed in this pull request?
(Please fill in changes proposed in this fix)
## How was this patch tested?
(Please explain how this
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18228
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/79456/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18228
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/18228
**[Test build #79456 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/79456/testReport)**
for PR 18228 at commit
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/18581
Will clean up soon.
---
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 srowen commented on the issue:
https://github.com/apache/spark/pull/18586
Your new test looks reasonable, though it failed, because I believe the
sorting is only by key. It wouldn't necessarily cause them to be ordered by the
second value in the tuple. The example is a
Github user wzhfy commented on a diff in the pull request:
https://github.com/apache/spark/pull/16422#discussion_r126386081
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/command/tables.scala ---
@@ -626,6 +624,120 @@ case class DescribeTableCommand(
}
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18586
**[Test build #3840 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3840/testReport)**
for PR 18586 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18541
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/79453/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18541
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/18541
**[Test build #79453 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/79453/testReport)**
for PR 18541 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18460
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 kiszk commented on the issue:
https://github.com/apache/spark/pull/18571
@gatorsmile could you please review this?
---
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/18460
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/79454/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18460
**[Test build #79454 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/79454/testReport)**
for PR 18460 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18565
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/79452/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18565
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/18565
**[Test build #79452 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/79452/testReport)**
for PR 18565 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18571
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/79450/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18571
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 skonto commented on a diff in the pull request:
https://github.com/apache/spark/pull/18587#discussion_r126382374
--- Diff: core/src/main/scala/org/apache/spark/deploy/SparkSubmit.scala ---
@@ -269,6 +269,25 @@ object SparkSubmit extends CommandLineUtils {
}
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18587
**[Test build #79462 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/79462/testReport)**
for PR 18587 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18581
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/79455/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18571
**[Test build #79450 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/79450/testReport)**
for PR 18571 at commit
GitHub user skonto opened a pull request:
https://github.com/apache/spark/pull/18587
[SPARK-12559][mesos] fix --packages for mesos
## What changes were proposed in this pull request?
Fixes --packages flag for mesos in cluster mode. Probably I will handle
standalone and Yarn in
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18581
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/18581
**[Test build #79455 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/79455/testReport)**
for PR 18581 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18586
**[Test build #3840 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3840/testReport)**
for PR 18586 at commit
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/18586
The extra test is nice too, yeah. By the way if you change the title to
include `[SPARK-21358]` instead, it will automatically link to the JIRA.
---
If your project is set up for it, you can reply
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18586
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 chie8842 opened a pull request:
https://github.com/apache/spark/pull/18586
[Spark 21358][Examples] Argument of repartitionandsortwithinpartitions at
pyspark
## What changes were proposed in this pull request?
At example of repartitionAndSortWithinPartitions at
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/18585
I'd ask you to close this and back up and discuss what this is about on the
JIRA first. I don't understand what this is intended to do.
---
If your project is set up for it, you can reply to this
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/18584
Yes that's an important point I didn't mention. None of the shaded classes
appear in any API, except `private[mllib]` classes.
---
If your project is set up for it, you can reply to this email and
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18581
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/79448/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18581
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/18581
**[Test build #79448 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/79448/testReport)**
for PR 18581 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18498
**[Test build #79461 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/79461/testReport)**
for PR 18498 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18576
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/18576
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/79449/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18581
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/18576
**[Test build #79449 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/79449/testReport)**
for PR 18576 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18581
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/79446/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18581
**[Test build #79446 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/79446/testReport)**
for PR 18581 at commit
Github user zhengruifeng closed the pull request at:
https://github.com/apache/spark/pull/15324
---
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 HyukjinKwon commented on a diff in the pull request:
https://github.com/apache/spark/pull/18498#discussion_r126373703
--- Diff: R/pkg/R/schema.R ---
@@ -76,7 +76,7 @@ structType.structField <- function(x, ...) {
#' @rdname structType
#' @method structType
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18585
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 Shanshan-IC opened a pull request:
https://github.com/apache/spark/pull/18585
SPARK-21359
## What changes were proposed in this pull request?
As described in https://issues.apache.org/jira/browse/SPARK-21359
add new functions for frequency discretizer
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18555
**[Test build #79460 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/79460/testReport)**
for PR 18555 at commit
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/18581
Let me cc @gatorsmile and @maropu who I believe are interested in this.
---
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 vruusmann commented on the issue:
https://github.com/apache/spark/pull/18584
Good to know that there will be some relief coming in Apache Spark 2.3.X.
I don't think that the shading will break any Spark application that
depends on the `PMMLExportable` trait,
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18584
**[Test build #79459 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/79459/testReport)**
for PR 18584 at commit
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/18584
CC @vanzin for a look at the shading, as a sense check
maybe @jkbradley or @MLnick is interested in this change too.
@vruusmann later I think we could update to JPMML 1.3 too.
---
If
GitHub user srowen opened a pull request:
https://github.com/apache/spark/pull/18584
Shade JPMML
## What changes were proposed in this pull request?
Shade JPMML classes (`org.jpmml.**`) and related PMML model classes
(`org.dmg.pmml.**`). This insulates downstream users
Github user kiszk commented on a diff in the pull request:
https://github.com/apache/spark/pull/18574#discussion_r126365395
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/analysis/FunctionRegistry.scala
---
@@ -112,7 +112,12 @@ class SimpleFunctionRegistry
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18583
**[Test build #79458 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/79458/testReport)**
for PR 18583 at commit
GitHub user aokolnychyi opened a pull request:
https://github.com/apache/spark/pull/18583
[SPARK-21332][SQL] Incorrect result type inferred for some decimal
expressions
## What changes were proposed in this pull request?
This PR changes the direction of expression
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18300
**[Test build #79457 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/79457/testReport)**
for PR 18300 at commit
Github user 10110346 commented on a diff in the pull request:
https://github.com/apache/spark/pull/18228#discussion_r126359992
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/stringExpressions.scala
---
@@ -1199,6 +1199,82 @@ case class
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18228
**[Test build #79456 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/79456/testReport)**
for PR 18228 at commit
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/18581
cc @cloud-fan, could you take a look please when you have some time?
---
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 HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/18581
I guess we need few more tests about CSV and changes. Let me leave this out
in the documentation here for now.
Few more test cases should be about writing out with a custom line
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18582
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/79451/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18582
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/18582
**[Test build #79451 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/79451/testReport)**
for PR 18582 at commit
Github user maropu commented on the issue:
https://github.com/apache/spark/pull/17758
@cloud-fan Thanks! BTW, we better handle other duplication (e.g., local
temporary tables)?;
```
scala> Seq((1, 1)).toDF("a", "a").createOrReplaceTempView("t")
scala> sql("SELECT * FROM
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18581
**[Test build #79455 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/79455/testReport)**
for PR 18581 at commit
Github user MLnick commented on a diff in the pull request:
https://github.com/apache/spark/pull/18305#discussion_r126357847
--- Diff:
mllib/src/test/scala/org/apache/spark/ml/optim/aggregator/LogisticAggregatorSuite.scala
---
@@ -0,0 +1,254 @@
+/*
+ * Licensed to the
Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/18574#discussion_r126356309
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/analysis/FunctionRegistry.scala
---
@@ -112,7 +112,12 @@ class
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/17758
---
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/17758
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
301 - 400 of 497 matches
Mail list logo
