Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15457
**[Test build #66869 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/66869/consoleFull)**
for PR 15457 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15416
**[Test build #3337 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3337/consoleFull)**
for PR 15416 at commit
Github user loneknightpy commented on the issue:
https://github.com/apache/spark/pull/15285
@tdas Based on our offline discussion, I added file size cache for the
compressed log files.
---
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/15416
**[Test build #3337 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3337/consoleFull)**
for PR 15416 at commit
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/15452
---
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/15414
**[Test build #66872 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/66872/consoleFull)**
for PR 15414 at commit
Github user rxin commented on the issue:
https://github.com/apache/spark/pull/15452
Merging in master/branch-2.0.
---
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/15285
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/66865/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15285
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/15285
**[Test build #66865 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/66865/consoleFull)**
for PR 15285 at commit
Github user rxin commented on the issue:
https://github.com/apache/spark/pull/15432
Given different databases diverge (they don't even have the same function
names), I think it's fine to just have null be treated as 0 like Hive/MySQL.
---
If your project is set up for it, you can
Github user jerryshao commented on a diff in the pull request:
https://github.com/apache/spark/pull/15456#discussion_r83146972
--- Diff: core/src/main/scala/org/apache/spark/deploy/SparkSubmit.scala ---
@@ -104,6 +104,8 @@ object SparkSubmit {
/___/ .__/\_,_/_/ /_/\_\
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/15432
Oh, strictly, it does not ignore in case of `PostgreSQL`. It unsets.
```sql
postgres=# SELECT setseed(0);
setseed
-
(1 row)
postgres=# SELECT
Github user cloud-fan commented on the issue:
https://github.com/apache/spark/pull/15230
LGTM except one minor comment
---
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 viirya commented on a diff in the pull request:
https://github.com/apache/spark/pull/15148#discussion_r83146607
--- Diff: mllib/src/main/scala/org/apache/spark/ml/feature/LSH.scala ---
@@ -0,0 +1,343 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF)
Github user viirya commented on the issue:
https://github.com/apache/spark/pull/15427
Thanks for review! @rxin @cloud-fan
---
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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/15427
---
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/15427
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 rxin commented on the issue:
https://github.com/apache/spark/pull/15272
hm looks like another legitimate failing test too
---
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 rxin commented on the issue:
https://github.com/apache/spark/pull/14702
@tejasapatil looks like there is a legitimate failing 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
Github user rxin commented on the issue:
https://github.com/apache/spark/pull/15458
LGTM pending Jenkins.
---
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/15458
**[Test build #66871 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/66871/consoleFull)**
for PR 15458 at commit
GitHub user cloud-fan opened a pull request:
https://github.com/apache/spark/pull/15458
[SPARK-17899][SQL] add a debug mode to keep raw table properties in
HiveExternalCatalog
## What changes were proposed in this pull request?
Currently `HiveExternalCatalog` will filter
Github user cloud-fan commented on the issue:
https://github.com/apache/spark/pull/15458
cc @yhuai
---
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 gatorsmile commented on the issue:
https://github.com/apache/spark/pull/15432
Now, at least we have four options, when users setting `NULL` as a seed
number for `rand`:
1. Hive/MySQL - `NULL` is equivalent to `0`
2. DB2 - when the seed is `NULL`, `rand` returns
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/15437
---
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 HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/15432
Ah, PostgreSQL seems unsetting the seed.
```
postgres=# SELECT setseed(0), random(), random();
setseed | random | random
Github user zsxwing commented on the issue:
https://github.com/apache/spark/pull/15437
LGTM. Thanks! Merging to master and 2.0.
---
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/15456
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/66862/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15456
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/15456
**[Test build #66862 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/66862/consoleFull)**
for PR 15456 at commit
Github user wangmiao1981 commented on a diff in the pull request:
https://github.com/apache/spark/pull/15365#discussion_r83143464
--- Diff: R/pkg/R/mllib.R ---
@@ -647,6 +654,195 @@ setMethod("predict", signature(object =
"KMeansModel"),
predict_internal(object,
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/15432
What is the behavior of `PostgreSQL`? Treating `NULL` as zero?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/15432
Not urgent but in my experience such PR have been being hold. So, I am
trying to fix the problem specified in the JIRA only rather than fixing others
together.
@srowen said "I'm not
Github user tnachen commented on the issue:
https://github.com/apache/spark/pull/12933
I just tried running it locally and I'm getting the same error. It seems
like with your change that test is simply declining the offer.
---
If your project is set up for it, you can reply to this
Github user priyankagargnitk commented on the issue:
https://github.com/apache/spark/pull/15449
Thanks rxin
---
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 gatorsmile commented on the issue:
https://github.com/apache/spark/pull/15432
At first, we do not strictly follow Hive. You can easily find many in
Spark. I do not think this is an urgent JIRA, right? Like what @srowen replied
in the JIRA, he does not think this is a bug.
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15408
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/15408
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/66860/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15408
**[Test build #66860 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/66860/consoleFull)**
for PR 15408 at commit
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/15432
Strictly, the JIRA describes handling `null` and we might not have to
generalize the cases further.
> it will failed when do select rand(null)
Also, I would like to add the
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/9766
**[Test build #66870 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/66870/consoleFull)**
for PR 9766 at commit
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/15432
Unfortunately, not all the things have a standard to follow. That is why I
suggested you to do a research about it. Like Oracle, it does not have such a
function in their SQL-function list:
Github user mallman commented on a diff in the pull request:
https://github.com/apache/spark/pull/14690#discussion_r83141382
--- Diff:
sql/hive/src/main/scala/org/apache/spark/sql/hive/HiveExternalCatalog.scala ---
@@ -616,6 +617,44 @@ private[spark] class
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15457
**[Test build #66869 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/66869/consoleFull)**
for PR 15457 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/9766
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/66868/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/9766
**[Test build #66868 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/66868/consoleFull)**
for PR 9766 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/9766
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 sethah commented on the issue:
https://github.com/apache/spark/pull/15435
So, based on my interpretation of this and how this can actually work, we
need to have:
scala
sealed trait LogisticRegressionSummary
sealed trait
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/9766
**[Test build #66868 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/66868/consoleFull)**
for PR 9766 at commit
GitHub user rxin opened a pull request:
https://github.com/apache/spark/pull/15457
[SPARK-17830][SQL] Annotate remaining SQL APIs with InterfaceStability
## What changes were proposed in this pull request?
This patch annotates all the remaining APIs in SQL (excluding streaming)
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15457
**[Test build #66867 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/66867/consoleFull)**
for PR 15457 at commit
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/15457#discussion_r83140489
--- Diff: sql/core/src/main/java/org/apache/spark/sql/api/java/UDF1.java ---
@@ -19,14 +19,12 @@
import java.io.Serializable;
-//
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/15457#discussion_r83140501
--- Diff: sql/core/src/main/java/org/apache/spark/sql/api/java/UDF1.java ---
@@ -19,14 +19,12 @@
import java.io.Serializable;
-//
Github user dafrista closed the pull request at:
https://github.com/apache/spark/pull/15455
---
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 AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/9766
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 sethah commented on the issue:
https://github.com/apache/spark/pull/15435
So I've been reading through some of the history with logistic regression
summaries. There was a lot of discussion on how to design the abstractions for
this,
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/9766
**[Test build #66866 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/66866/consoleFull)**
for PR 9766 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/9766
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/66866/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/9766
**[Test build #66866 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/66866/consoleFull)**
for PR 9766 at commit
Github user rxin commented on the issue:
https://github.com/apache/spark/pull/15455
Merging in. Thanks.
Can you also close the pr? GitHub wont' close it automatically because it
is not merged into master branch.
---
If your project is set up for it, you can reply to this
Github user viirya commented on a diff in the pull request:
https://github.com/apache/spark/pull/15427#discussion_r83140093
--- Diff: sql/core/src/main/scala/org/apache/spark/sql/Dataset.scala ---
@@ -1878,17 +1878,25 @@ class Dataset[T] private[sql](
def
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14690
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/66861/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14690
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/14690
**[Test build #66861 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/66861/consoleFull)**
for PR 14690 at commit
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/15432
Initially, this JIRA was only handling `null` as seed. If you both worry
the change here, I would like to make the PR smaller as suggested initially.
---
If your project is set up for it, you
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/15432
That is a great reference. However, is this the function described in a
standard? I guess it is different for each implementation of database. For
example,
> The result can be null;
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15285
**[Test build #66865 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/66865/consoleFull)**
for PR 15285 at commit
Github user sethah commented on the issue:
https://github.com/apache/spark/pull/15414
Thanks, I'll take a more detailed look in the next couple of days. Let's
also wait and see if we can get @yanboliang or @jkbradley to give an opinion.
---
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/15230#discussion_r83138864
--- Diff:
sql/hive/src/main/scala/org/apache/spark/sql/hive/HiveExternalCatalog.scala ---
@@ -111,6 +111,10 @@ private[spark] class
Github user sethah commented on a diff in the pull request:
https://github.com/apache/spark/pull/15414#discussion_r83057213
--- Diff: mllib/src/test/scala/org/apache/spark/ml/PredictorSuite.scala ---
@@ -0,0 +1,80 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF)
Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/15230#discussion_r83138671
--- Diff:
sql/hive/src/main/scala/org/apache/spark/sql/hive/HiveExternalCatalog.scala ---
@@ -111,6 +111,10 @@ private[spark] class
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15285
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/15285
**[Test build #66864 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/66864/consoleFull)**
for PR 15285 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15285
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/66864/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15307
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/66859/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15307
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/15307
**[Test build #66859 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/66859/consoleFull)**
for PR 15307 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15285
**[Test build #66864 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/66864/consoleFull)**
for PR 15285 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15285
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/15285
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/66863/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15285
**[Test build #66863 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/66863/consoleFull)**
for PR 15285 at commit
Github user zhengruifeng commented on the issue:
https://github.com/apache/spark/pull/15414
@sethah I have maken some modification according to the comments
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15285
**[Test build #66863 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/66863/consoleFull)**
for PR 15285 at commit
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/15432
Let me show you an example:
https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/sqlref/src/tpc/db2z_bif_rand.html
This is the official document of `rand` in DB2 z/OS. Below is
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/15402
---
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 yanboliang commented on the issue:
https://github.com/apache/spark/pull/15402
Merged into master. Thanks for review. @zhengruifeng
---
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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/15406
---
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 yanboliang commented on the issue:
https://github.com/apache/spark/pull/15406
LGTM2, merged into master. 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 zjffdu commented on a diff in the pull request:
https://github.com/apache/spark/pull/9766#discussion_r83134970
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/UDFRegistration.scala ---
@@ -414,6 +418,84 @@ class UDFRegistration private[sql] (functionRegistry:
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15408
**[Test build #66860 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/66860/consoleFull)**
for PR 15408 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15456
**[Test build #66862 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/66862/consoleFull)**
for PR 15456 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15307
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/66858/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15307
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 jerryshao commented on the issue:
https://github.com/apache/spark/pull/15253
@zsxwing , would you mind taking a look at this fix for 1.6 branch, 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.
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15307
**[Test build #66858 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/66858/consoleFull)**
for PR 15307 at commit
GitHub user jerryshao opened a pull request:
https://github.com/apache/spark/pull/15456
[SPARK-17686][Core] Support printing out scala and java version with
spark-submit --version command
## What changes were proposed in this pull request?
In our universal gateway service
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14690
**[Test build #66861 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/66861/consoleFull)**
for PR 14690 at commit
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/15432
(Oh, I am making a comment via my phone. Sorry for occasional closing and
reopening here..)
---
If your project is set up for it, you can reply to this email and have your
reply appear on
GitHub user HyukjinKwon reopened a pull request:
https://github.com/apache/spark/pull/15432
[SPARK-17854][SQL] rand/randn allows null/long as input seed
## What changes were proposed in this pull request?
This PR proposes `rand`/`randn` accept `null` as input in Scala/SQL
1 - 100 of 690 matches
Mail list logo
