Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17553
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/75582/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17553
**[Test build #75582 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/75582/testReport)**
for PR 17553 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17540
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/75581/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17540
**[Test build #75581 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/75581/testReport)**
for PR 17540 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17540
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/17553
**[Test build #75582 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/75582/testReport)**
for PR 17553 at commit
Github user actuaryzhang commented on the issue:
https://github.com/apache/spark/pull/17553
@felixcheung
---
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 actuaryzhang opened a pull request:
https://github.com/apache/spark/pull/17553
[SPARK-20026][Doc] Add Tweedie example for SparkR in programming guide
## What changes were proposed in this pull request?
Add Tweedie example for SparkR in programming guide.
The doc
Github user squito commented on the issue:
https://github.com/apache/spark/pull/16354
closing this since on the jira we decided that a different approach is
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
Github user squito closed the pull request at:
https://github.com/apache/spark/pull/16354
---
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 vanzin commented on the issue:
https://github.com/apache/spark/pull/17551
> Our use case involves jobs running in a remote cluster without a Spark
master.
It's still running your code, right? Why can't you add a configuration to
your own code that tells it to
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17552
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/75578/
Test FAILed.
---
Github user rdblue commented on the issue:
https://github.com/apache/spark/pull/17540
The new test failures are caused by a check I inserted. Moving where
`withNewExecutionId` gets called could result in missing SQL queries in the UI,
so anywhere I'm replacing `withNewExecutionId`
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17552
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/17540
**[Test build #75581 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/75581/testReport)**
for PR 17540 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17552
**[Test build #75578 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/75578/testReport)**
for PR 17552 at commit
Github user squito commented on the issue:
https://github.com/apache/spark/pull/14617
btw, anybody interested in looking at getting the memory to show up in the
history server as well? this issue we were discussing earlier:
>> AFAIK we don't record block update events in
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17540
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/17540
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/75579/
Test FAILed.
---
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/14617
---
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/17540
**[Test build #75579 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/75579/testReport)**
for PR 17540 at commit
Github user squito commented on the issue:
https://github.com/apache/spark/pull/14617
merged to master. Thanks @jerryshao
---
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/17500
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/17500
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/75576/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17500
**[Test build #75576 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/75576/testReport)**
for PR 17500 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17541
**[Test build #75580 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/75580/testReport)**
for PR 17541 at commit
Github user dgingrich commented on the issue:
https://github.com/apache/spark/pull/16845
Great, thanks Holden!
---
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 a diff in the pull request:
https://github.com/apache/spark/pull/17541#discussion_r110223590
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/plans/QueryPlan.scala
---
@@ -372,49 +410,19 @@ abstract class QueryPlan[PlanType
Github user ioana-delaney commented on a diff in the pull request:
https://github.com/apache/spark/pull/17546#discussion_r110221774
--- Diff:
sql/catalyst/src/test/scala/org/apache/spark/sql/catalyst/optimizer/StarJoinCostBasedReorderSuite.scala
---
@@ -0,0 +1,426 @@
+/*
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17540
**[Test build #75579 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/75579/testReport)**
for PR 17540 at commit
Github user jkbradley commented on the issue:
https://github.com/apache/spark/pull/17494
LGTM if others are ok 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
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17552
**[Test build #75578 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/75578/testReport)**
for PR 17552 at commit
Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/17541#discussion_r110218239
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/datasources/LogicalRelation.scala
---
@@ -51,27 +51,11 @@ case class LogicalRelation(
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17541
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/75577/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17541
Merged build finished. Test FAILed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
Github user vanzin commented on the issue:
https://github.com/apache/spark/pull/16788
Hello all, if you're not going to update this PR then it should be closed.
---
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 SparkQA commented on the issue:
https://github.com/apache/spark/pull/17541
**[Test build #75577 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/75577/testReport)**
for PR 17541 at commit
Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/17552#discussion_r110217881
--- Diff:
sql/core/src/test/scala/org/apache/spark/sql/sources/PathOptionSuite.scala ---
@@ -75,13 +75,13 @@ class PathOptionSuite extends DataSourceTest
Github user cloud-fan commented on the issue:
https://github.com/apache/spark/pull/17552
cc @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 and wishes so,
GitHub user cloud-fan opened a pull request:
https://github.com/apache/spark/pull/17552
[SPARK-20245][SQL][minor] pass output to LogicalRelation directly
## What changes were proposed in this pull request?
Currently `LogicalRelation` has a `expectedOutputAttributes`
Github user ioana-delaney commented on a diff in the pull request:
https://github.com/apache/spark/pull/17546#discussion_r110213152
--- Diff:
sql/catalyst/src/test/scala/org/apache/spark/sql/catalyst/optimizer/StarJoinCostBasedReorderSuite.scala
---
@@ -0,0 +1,426 @@
+/*
Github user ioana-delaney commented on a diff in the pull request:
https://github.com/apache/spark/pull/17546#discussion_r110212976
--- Diff:
sql/catalyst/src/test/scala/org/apache/spark/sql/catalyst/optimizer/StarJoinCostBasedReorderSuite.scala
---
@@ -0,0 +1,426 @@
+/*
Github user dilipbiswal commented on a diff in the pull request:
https://github.com/apache/spark/pull/17541#discussion_r110212520
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/plans/QueryPlan.scala
---
@@ -359,9 +359,47 @@ abstract class QueryPlan[PlanType
Github user barnardb commented on the issue:
https://github.com/apache/spark/pull/17551
Our use case involves jobs running in a remote cluster without a Spark
master. I agree that the history server is the better to solve this, but we'd
like to get a solution that doesn't depend on a
Github user ioana-delaney commented on a diff in the pull request:
https://github.com/apache/spark/pull/17546#discussion_r110211908
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/optimizer/CostBasedJoinReorder.scala
---
@@ -327,3 +345,104 @@ object
Github user ioana-delaney commented on a diff in the pull request:
https://github.com/apache/spark/pull/17546#discussion_r110211689
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/optimizer/CostBasedJoinReorder.scala
---
@@ -327,3 +345,104 @@ object
Github user ioana-delaney commented on a diff in the pull request:
https://github.com/apache/spark/pull/17546#discussion_r110211394
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/optimizer/CostBasedJoinReorder.scala
---
@@ -327,3 +345,104 @@ object
Github user ioana-delaney commented on a diff in the pull request:
https://github.com/apache/spark/pull/17546#discussion_r110210819
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/optimizer/CostBasedJoinReorder.scala
---
@@ -327,3 +345,104 @@ object
Github user rdblue commented on the issue:
https://github.com/apache/spark/pull/17540
@cloud-fan, can you look at this? What do you think about the question
above: when should `withNewExecutionId` get called?
---
If your project is set up for it, you can reply to this email and have
Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/17541#discussion_r110208947
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/plans/QueryPlan.scala
---
@@ -372,49 +410,19 @@ abstract class QueryPlan[PlanType <:
Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/17541#discussion_r110208623
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/plans/QueryPlan.scala
---
@@ -372,49 +410,19 @@ abstract class QueryPlan[PlanType <:
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/17511
---
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 felixcheung commented on the issue:
https://github.com/apache/spark/pull/17511
merged 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 wishes
Github user felixcheung commented on the issue:
https://github.com/apache/spark/pull/17512
merged to 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
enabled and
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/17512
---
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 d2r commented on the issue:
https://github.com/apache/spark/pull/17500
@srowen
> Hm, why does this help? isn't it somehow trying to bind/close a port
that's already in use?
If the port is in use, then it will throw a BindException here, which will
be
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17541
**[Test build #75577 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/75577/testReport)**
for PR 17541 at commit
Github user gatorsmile commented on a diff in the pull request:
https://github.com/apache/spark/pull/17541#discussion_r110199279
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/plans/QueryPlan.scala
---
@@ -372,49 +410,19 @@ abstract class QueryPlan[PlanType
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/17534#discussion_r110198657
--- Diff: docs/monitoring.md ---
@@ -299,12 +299,12 @@ can be identified by their `[attempt-id]`. In the API
listed below, when running
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17500
**[Test build #75576 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/75576/testReport)**
for PR 17500 at commit
Github user ajbozarth commented on the issue:
https://github.com/apache/spark/pull/17551
I agree with @srowen and @jerryshao this is what the history server is for
---
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 tgravescs commented on the issue:
https://github.com/apache/spark/pull/17500
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 and
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17459
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/75575/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17459
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/17459
**[Test build #75575 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/75575/testReport)**
for PR 17459 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17494
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/75574/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17494
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/17494
**[Test build #75574 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/75574/testReport)**
for PR 17494 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17459
**[Test build #75575 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/75575/testReport)**
for PR 17459 at commit
Github user johnc1231 commented on the issue:
https://github.com/apache/spark/pull/17459
@viirya Added appropriate tests, back to 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
Github user johnc1231 commented on a diff in the pull request:
https://github.com/apache/spark/pull/17459#discussion_r110163778
--- Diff:
mllib/src/test/scala/org/apache/spark/mllib/linalg/distributed/IndexedRowMatrixSuite.scala
---
@@ -89,11 +89,19 @@ class IndexedRowMatrixSuite
Github user jerryshao commented on the issue:
https://github.com/apache/spark/pull/17551
Agree with @srowen , the proposed solution overlaps the key functionality
of history server. Usually we should stop the app and release the resources as
soon as application finished. This
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17494
**[Test build #75574 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/75574/testReport)**
for PR 17494 at commit
Github user viirya commented on a diff in the pull request:
https://github.com/apache/spark/pull/17494#discussion_r110161378
--- Diff: python/pyspark/ml/stat.py ---
@@ -71,6 +71,67 @@ def test(dataset, featuresCol, labelCol):
return _java2py(sc,
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 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/75573/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17222
**[Test build #75573 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/75573/testReport)**
for PR 17222 at commit
Github user MLnick commented on a diff in the pull request:
https://github.com/apache/spark/pull/17494#discussion_r110156124
--- Diff: python/pyspark/ml/stat.py ---
@@ -71,6 +71,67 @@ def test(dataset, featuresCol, labelCol):
return _java2py(sc,
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17551
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 srowen commented on the issue:
https://github.com/apache/spark/pull/17551
I would oppose this change. It is what the history server is for. Or also
profiling tools, or simple debugging mechanisms you allude to. It doesn't
belong as yet another flag in Spark
---
If your
GitHub user barnardb opened a pull request:
https://github.com/apache/spark/pull/17551
[SPARK-20242][Web UI] Add spark.ui.stopDelay
## What changes were proposed in this pull request?
Adds a spark.ui.stopDelay configuration property that can be used to keep
the UI running
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17527
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/75572/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17527
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/17527
**[Test build #75572 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/75572/testReport)**
for PR 17527 at commit
Github user yssharma commented on the issue:
https://github.com/apache/spark/pull/17506
Thanks @srowen
---
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/17550
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 zenglinxi0615 opened a pull request:
https://github.com/apache/spark/pull/17550
[SPARK-20240][SQL] SparkSQL support limitations of max dynamic partitâ¦
â¦ions when inserting hive table
## What changes were proposed in this pull request?
support limitations
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17222
**[Test build #75573 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/75573/testReport)**
for PR 17222 at commit
Github user holdenk commented on the issue:
https://github.com/apache/spark/pull/16845
Let's make sure everything is still fine since we've made some changes in
the testing infrastructure though - if it passes I'll merge this tonight
(european time).
Jenkins retest this
Github user holdenk commented on the issue:
https://github.com/apache/spark/pull/16845
LGTM - sorry for the slowness.
---
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/17222
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/75571/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17222
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/17222
**[Test build #75571 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/75571/testReport)**
for PR 17222 at commit
Github user yuananf commented on the issue:
https://github.com/apache/spark/pull/17505
@wangyum @rxin @gatorsmile Is it possible to upgrade the built-in
hive-exec to resolve this problem?
I believe the built-in hive-exec is this
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17222
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/17222
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/75570/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17222
**[Test build #75570 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/75570/testReport)**
for PR 17222 at commit
Github user MLnick commented on the issue:
https://github.com/apache/spark/pull/16158
Sorry this slipped! I'd like to revisit soon after 2.2. settles down.
I think we may need to consider how this integrates with training /
evaluation summaries to create a holistic solution
Github user holdenk commented on a diff in the pull request:
https://github.com/apache/spark/pull/17494#discussion_r110127639
--- Diff: python/pyspark/ml/stat.py ---
@@ -71,6 +71,67 @@ def test(dataset, featuresCol, labelCol):
return _java2py(sc,
Github user yuananf commented on the issue:
https://github.com/apache/spark/pull/15726
@viirya Is it possible to upgrade the built-in hive-exec to resolve this
problem? We are facing the same problem, insert overwrite dynamic partition is
extremely slow, the data written is over in 5
101 - 200 of 305 matches
Mail list logo
