GitHub user kishorbp opened a pull request:
https://github.com/apache/spark/pull/16752
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 patch
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/16751
---
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 viirya commented on the issue:
https://github.com/apache/spark/pull/16751
LGTM 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 feature
enabled and wishes so, or if the
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16043
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/14412
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/72187/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13932
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/16043
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/72189/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14412
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/13932
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/72188/
Test FAILed.
---
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/16752
Hi @kishorbp , it seems mistakenly open. Would you please close 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 kishorbp closed the pull request at:
https://github.com/apache/spark/pull/16752
---
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/16751
**[Test build #72191 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72191/testReport)**
for PR 16751 at commit
GitHub user HyukjinKwon opened a pull request:
https://github.com/apache/spark/pull/16753
[SPARK-19296][SQL] Deduplicate arguments in JdbcUtils.saveTable
## What changes were proposed in this pull request?
This PR deduplicates arguments, `url` and `table` in `JdbcUtils`.
Github user viirya commented on the issue:
https://github.com/apache/spark/pull/16751
The dependency change looks clear.
---
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 HyukjinKwon commented on a diff in the pull request:
https://github.com/apache/spark/pull/16750#discussion_r98629735
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/DataFrameReader.scala ---
@@ -329,7 +332,17 @@ class DataFrameReader private[sql](sparkSession:
Github user HyukjinKwon commented on a diff in the pull request:
https://github.com/apache/spark/pull/16750#discussion_r98625766
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/datasources/csv/CSVOptions.scala
---
@@ -161,12 +163,3 @@ private[csv] class
Github user HyukjinKwon commented on a diff in the pull request:
https://github.com/apache/spark/pull/16750#discussion_r98624418
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/DataFrameReader.scala ---
@@ -329,7 +332,17 @@ class DataFrameReader private[sql](sparkSession:
Github user HyukjinKwon commented on a diff in the pull request:
https://github.com/apache/spark/pull/16750#discussion_r98623217
--- Diff: python/pyspark/sql/readwriter.py ---
@@ -297,7 +300,7 @@ def text(self, paths):
def csv(self, path, schema=None, sep=None,
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16752
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 HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/16753
Hi @gatorsmile, could you take a look for this one please? (It might not
need a JIRA but it happened to be opened by someone).
---
If your project is set up for it, you can reply to this email
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/16753
It's true, though I wonder if it's still by design, that these methods take
url and table as important first-class arguments, and then also other options,
even though the options also contain the
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16750
**[Test build #72190 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72190/testReport)**
for PR 16750 at commit
Github user hvanhovell commented on a diff in the pull request:
https://github.com/apache/spark/pull/16043#discussion_r98613798
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/optimizer/ComplexTypes.scala
---
@@ -0,0 +1,166 @@
+/*
+ * Licensed to the
Github user felixcheung commented on a diff in the pull request:
https://github.com/apache/spark/pull/16689#discussion_r98615769
--- Diff: R/pkg/R/DataFrame.R ---
@@ -1138,6 +1138,11 @@ setMethod("collect",
if (!is.null(PRIMITIVE_TYPES[[colType]]) && colType
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16750
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/16750
**[Test build #72190 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72190/testReport)**
for PR 16750 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16750
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/72190/
Test PASSed.
---
Github user rxin commented on the issue:
https://github.com/apache/spark/pull/16751
Merging in 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 wishes so, or
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16751
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/72191/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16751
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 ueshin opened a pull request:
https://github.com/apache/spark/pull/16750
[SPARK-18937][SQL] Timezone support in CSV/JSON parsing
## What changes were proposed in this pull request?
This is a follow-up pr of #16308.
This pr enables timezone support in
GitHub user dongjoon-hyun opened a pull request:
https://github.com/apache/spark/pull/16751
[SPARK-19409][BUILD] Bump parquet version to 1.8.2
## What changes were proposed in this pull request?
Apache Parquet 1.8.2 is released officially last week on 26 Jan.
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16751
**[Test build #72191 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72191/testReport)**
for PR 16751 at commit
Github user dongjoon-hyun commented on the issue:
https://github.com/apache/spark/pull/16281
Hi, all.
Now, I'm trying to upgrade Apache Spark to 1.8.2.
---
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/16753
**[Test build #72192 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72192/testReport)**
for PR 16753 at commit
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/16747
@HyukjinKwon is this OK by you?
---
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/16758
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/16536
**[Test build #72219 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72219/testReport)**
for PR 16536 at commit
Github user dilipbiswal commented on a diff in the pull request:
https://github.com/apache/spark/pull/16759#discussion_r98807908
--- Diff:
sql/core/src/test/resources/sql-tests/results/subquery/in-subquery/not-in-group-by.sql.out
---
@@ -0,0 +1,150 @@
+-- Automatically
Github user sethah commented on the issue:
https://github.com/apache/spark/pull/9
ping! I could take this over if needed :)
---
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 holdenk commented on the issue:
https://github.com/apache/spark/pull/16536
Great, I'll wait for jenkins then :)
---
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/16536
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/16536
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/7/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16758
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/72217/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16758
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/16758
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/72223/
Test FAILed.
---
Github user sethah commented on the issue:
https://github.com/apache/spark/pull/16740
I agree having a special case is unsatisfying from an engineering
perspective. In Spark it's a bit different than R since every iteration of IRLS
will launch a Spark job, making a pass over the
Github user viirya commented on a diff in the pull request:
https://github.com/apache/spark/pull/16578#discussion_r98833717
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/planning/GetStructField2.scala
---
@@ -0,0 +1,33 @@
+/*
+ * Licensed to the
Github user gatorsmile commented on a diff in the pull request:
https://github.com/apache/spark/pull/16762#discussion_r98833830
--- Diff: sql/core/src/test/scala/org/apache/spark/sql/JoinSuite.scala ---
@@ -584,24 +602,37 @@ class JoinSuite extends QueryTest with
SharedSQLContext
Github user gatorsmile commented on a diff in the pull request:
https://github.com/apache/spark/pull/16762#discussion_r98833748
--- Diff: sql/core/src/test/scala/org/apache/spark/sql/JoinSuite.scala ---
@@ -215,18 +215,36 @@ class JoinSuite extends QueryTest with
SharedSQLContext
Github user viirya commented on a diff in the pull request:
https://github.com/apache/spark/pull/16578#discussion_r98833772
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/planning/GetStructField2.scala
---
@@ -0,0 +1,33 @@
+/*
+ * Licensed to the
Github user felixcheung commented on the issue:
https://github.com/apache/spark/pull/15279
What if we have a bunch of default values when arguments are not set, and
those are the values we could test with? This way the same sample code can run
with and without arguments?
---
If
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15415
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/72213/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15415
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/15415
**[Test build #72213 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72213/testReport)**
for PR 15415 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16722
**[Test build #72220 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72220/testReport)**
for PR 16722 at commit
Github user holdenk commented on the issue:
https://github.com/apache/spark/pull/16536
@zero323 that sounds like a good improvement.
---
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 holdenk commented on the issue:
https://github.com/apache/spark/pull/16727
The original PR was merged a few days ago, would you be OK with making a
new JIRA just to avoid confusion? You can make it related to the previous JIRA.
But otherwise looks good to me.
---
If
Github user jinxing64 commented on a diff in the pull request:
https://github.com/apache/spark/pull/16620#discussion_r98819685
--- Diff: core/src/main/scala/org/apache/spark/scheduler/DAGScheduler.scala
---
@@ -1212,8 +1223,9 @@ class DAGScheduler(
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16722
**[Test build #72225 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72225/testReport)**
for PR 16722 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16043
**[Test build #72229 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72229/testReport)**
for PR 16043 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16722
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/72225/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16722
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 wangmiao1981 opened a pull request:
https://github.com/apache/spark/pull/16761
[BackPort-2.1][SPARK-19319][SparkR]:SparkR Kmeans summary returns error
when the cluster size doesn't equal to k
## What changes were proposed in this pull request?
Backport fix of
Github user shivaram commented on a diff in the pull request:
https://github.com/apache/spark/pull/16720#discussion_r98833756
--- Diff: R/pkg/vignettes/sparkr-vignettes.Rmd ---
@@ -27,6 +27,9 @@ library(SparkR)
We use default settings in which it runs in local mode. It
Github user shivaram commented on a diff in the pull request:
https://github.com/apache/spark/pull/16720#discussion_r98833957
--- Diff: R/pkg/inst/tests/testthat/test_utils.R ---
@@ -17,6 +17,9 @@
context("functions in utils.R")
+# Ensure Spark is installed
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16762
**[Test build #72235 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72235/testReport)**
for PR 16762 at commit
Github user zhengruifeng commented on the issue:
https://github.com/apache/spark/pull/16727
@holdenk I created another jira to track this issue. Thanks all for
revewing!
---
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 holdenk commented on a diff in the pull request:
https://github.com/apache/spark/pull/16536#discussion_r98801781
--- Diff: python/pyspark/sql/functions.py ---
@@ -1826,23 +1826,35 @@ class UserDefinedFunction(object):
def __init__(self, func, returnType,
Github user zero323 commented on the issue:
https://github.com/apache/spark/pull/16536
@holdenk I have one more suggestion. Shouldn't we replace
```python
def _create_judf(self):
from pyspark.sql import SparkSession
sc =
Github user sethah commented on the issue:
https://github.com/apache/spark/pull/15628
ping @imatiach-msft @dbtsai
---
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 dilipbiswal commented on a diff in the pull request:
https://github.com/apache/spark/pull/16759#discussion_r98807939
--- Diff:
sql/core/src/test/resources/sql-tests/results/subquery/in-subquery/in-order-by.sql.out
---
@@ -0,0 +1,328 @@
+-- Automatically generated
Github user dilipbiswal commented on a diff in the pull request:
https://github.com/apache/spark/pull/16759#discussion_r98807968
--- Diff:
sql/core/src/test/resources/sql-tests/results/subquery/in-subquery/in-limit.sql.out
---
@@ -0,0 +1,147 @@
+-- Automatically generated by
Github user sethah commented on the issue:
https://github.com/apache/spark/pull/15435
sorry for the delay, hope to get to it 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
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/16536
---
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/16758
**[Test build #72217 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72217/testReport)**
for PR 16758 at commit
Github user mridulm commented on the issue:
https://github.com/apache/spark/pull/16603
Thanks for the review @vanzin , I will leave this open for a day in case
someone else also wants to review; and will commit tomorrow.
---
If your project is set up for it, you can reply to this
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16722
**[Test build #72225 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72225/testReport)**
for PR 16722 at commit
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/16735
BTW, @sergey-rubtsov, could you check if we should add a type-widening rule
in `findTightestCommonType` between `DateType` and `TimestampType`?
---
If your project is set up for it, you can
Github user zero323 commented on the issue:
https://github.com/apache/spark/pull/16536
@holdenk Done :)
---
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
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16722
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/72220/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16722
**[Test build #72220 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72220/testReport)**
for PR 16722 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16722
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/16620
**[Test build #72226 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72226/testReport)**
for PR 16620 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16690
**[Test build #72228 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72228/testReport)**
for PR 16690 at commit
Github user felixcheung commented on a diff in the pull request:
https://github.com/apache/spark/pull/16720#discussion_r98834936
--- Diff: R/pkg/inst/tests/testthat/test_utils.R ---
@@ -17,6 +17,9 @@
context("functions in utils.R")
+# Ensure Spark is installed
Github user felixcheung commented on a diff in the pull request:
https://github.com/apache/spark/pull/16720#discussion_r98834935
--- Diff: R/pkg/vignettes/sparkr-vignettes.Rmd ---
@@ -27,6 +27,9 @@ library(SparkR)
We use default settings in which it runs in local mode.
Github user marmbrus commented on a diff in the pull request:
https://github.com/apache/spark/pull/16758#discussion_r98802935
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/StateImpl.scala ---
@@ -0,0 +1,70 @@
+/*
+ * Licensed to the Apache Software
Github user marmbrus commented on a diff in the pull request:
https://github.com/apache/spark/pull/16758#discussion_r98802826
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/StateImpl.scala ---
@@ -0,0 +1,70 @@
+/*
+ * Licensed to the Apache Software
Github user zero323 commented on a diff in the pull request:
https://github.com/apache/spark/pull/16536#discussion_r98802783
--- Diff: python/pyspark/sql/functions.py ---
@@ -1826,23 +1826,35 @@ class UserDefinedFunction(object):
def __init__(self, func, returnType,
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16760
**[Test build #72208 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72208/testReport)**
for PR 16760 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16536
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/72219/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16536
**[Test build #72219 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72219/testReport)**
for PR 16536 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16536
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/16536
**[Test build #7 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/7/testReport)**
for PR 16536 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16536
**[Test build #7 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/7/testReport)**
for PR 16536 at commit
Github user sethah commented on the issue:
https://github.com/apache/spark/pull/16740
I don't really expect that we'll be changing things so often that this
becomes a hassle. I think there is value in getting known results - in the
current test the IRLS solver takes 3 iterations to
Github user zsxwing commented on the issue:
https://github.com/apache/spark/pull/16725
LGTM pending tests
---
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/16725
**[Test build #72224 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72224/testReport)**
for PR 16725 at commit
Github user holdenk commented on the issue:
https://github.com/apache/spark/pull/16536
Going to go ahead and merge. Still need to sort out the JIRA permissions so
will take a bit for me to get that updated for you.
---
If your project is set up for it, you can reply to this email
1 - 100 of 399 matches
Mail list logo