Github user rberenguel commented on a diff in the pull request:
https://github.com/apache/spark/pull/18139#discussion_r119350488
--- Diff: python/pyspark/sql/types.py ---
@@ -187,8 +187,11 @@ def needConversion(self):
def toInternal(self, dt):
if dt is
Github user ScrapCodes commented on the issue:
https://github.com/apache/spark/pull/18143
Thanks @koeninger for taking a look. I did some testing to see if
performance was impacted, and made corrections.
---
If your project is set up for it, you can reply to this email and have
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18143
**[Test build #77590 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/77590/testReport)**
for PR 18143 at commit
Github user MLnick commented on a diff in the pull request:
https://github.com/apache/spark/pull/18022#discussion_r119347220
--- Diff:
mllib/src/test/scala/org/apache/spark/ml/recommendation/ALSSuite.scala ---
@@ -455,6 +487,22 @@ class ALSSuite
targetRMSE = 0.3)
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18157
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/18157
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/77586/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18157
**[Test build #77586 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/77586/testReport)**
for PR 18157 at commit
Github user facaiy commented on a diff in the pull request:
https://github.com/apache/spark/pull/18139#discussion_r119346663
--- Diff: python/pyspark/sql/types.py ---
@@ -187,8 +187,11 @@ def needConversion(self):
def toInternal(self, dt):
if dt is not
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/18022
---
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 srowen commented on the issue:
https://github.com/apache/spark/pull/18022
Merged to master/2.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 does not have this feature
enabled and wishes so,
Github user rberenguel commented on a diff in the pull request:
https://github.com/apache/spark/pull/18139#discussion_r119344936
--- Diff: python/pyspark/sql/types.py ---
@@ -187,8 +187,11 @@ def needConversion(self):
def toInternal(self, dt):
if dt is
Github user rberenguel commented on a diff in the pull request:
https://github.com/apache/spark/pull/18139#discussion_r119344927
--- Diff: python/pyspark/sql/types.py ---
@@ -187,8 +187,11 @@ def needConversion(self):
def toInternal(self, dt):
if dt is
Github user springcoil commented on the issue:
https://github.com/apache/spark/pull/16635
Came across this error today in Spark 2.1.0. Just adding this as a remark.
I had code like `nz_exp_test =
spark.read.parquet("dbfs:/experience_test/_NZ_2017-05-31-11-59-05.parquet")`
the error
Github user wangyum commented on a diff in the pull request:
https://github.com/apache/spark/pull/18153#discussion_r119340217
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/arithmetic.scala
---
@@ -97,20 +97,30 @@ case class UnaryPositive(child:
Github user holdenk commented on the issue:
https://github.com/apache/spark/pull/18161
LGTM
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18160
**[Test build #77589 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/77589/testReport)**
for PR 18160 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18159
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/77584/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18159
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/18159
**[Test build #77584 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/77584/testReport)**
for PR 18159 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18160
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/18160
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/77585/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18160
**[Test build #77585 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/77585/testReport)**
for PR 18160 at commit
Github user kiszk commented on a diff in the pull request:
https://github.com/apache/spark/pull/18153#discussion_r119332964
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/arithmetic.scala
---
@@ -97,20 +97,30 @@ case class UnaryPositive(child:
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18118
**[Test build #77588 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/77588/testReport)**
for PR 18118 at commit
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/18156
Try evaluating 3.1415f < 3.1415. It is true. Floating point representation
is inexact and in your example you explicitly choose the inexact representation
---
If your project is set up for it, you
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18161
**[Test build #77587 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/77587/testReport)**
for PR 18161 at commit
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/18161
@srowen and @holdenk, could you take a look please? I checked related codes
were updated by both of you before (and me as well).
---
If your project is set up for it, you can reply to this
GitHub user HyukjinKwon opened a pull request:
https://github.com/apache/spark/pull/18161
[MINOR][PYTHON] Ignore pep8 on test scripts in work directory generated in
tests
## What changes were proposed in this pull request?
Currently, if we run `./python/run-tests.py` and
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18157
**[Test build #77586 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/77586/testReport)**
for PR 18157 at commit
Github user wangyum commented on the issue:
https://github.com/apache/spark/pull/18157
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 AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18153
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/17113
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/77582/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18153
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/77583/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17113
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/18153
**[Test build #77583 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/77583/testReport)**
for PR 18153 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17113
**[Test build #77582 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/77582/testReport)**
for PR 17113 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17617
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/77581/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17617
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 10110346 commented on the issue:
https://github.com/apache/spark/pull/18156
I don't understand why the value of 3.1415f is actually something like
3.1414...
From the user's point of view, i think 3.142 maybe more reasonable.
---
If your project is set up for
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17617
**[Test build #77581 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/77581/testReport)**
for PR 17617 at commit
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/18074
---
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 srowen commented on the issue:
https://github.com/apache/spark/pull/18074
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 so, or
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18160
**[Test build #77585 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/77585/testReport)**
for PR 18160 at commit
GitHub user HyukjinKwon opened a pull request:
https://github.com/apache/spark/pull/18160
[SPARK-20938][SQL] Keep/print the string representation of catalyst filters
in metadata for CatalystScan
## What changes were proposed in this pull request?
Actual pushed-down
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/18152
Yes, I agree with that. It looks like there may be a similar instance in
`GradientDescent.scala`, where `bcWeights` is used in a `treeAggregate` but
then never destroyed.
In every other
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18155
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/77580/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18155
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/18155
**[Test build #77580 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/77580/testReport)**
for PR 18155 at commit
Github user ueshin commented on the issue:
https://github.com/apache/spark/pull/18155
LGTM, 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
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18155
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/18155
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/77579/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18155
**[Test build #77579 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/77579/testReport)**
for PR 18155 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18118
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 srowen commented on the issue:
https://github.com/apache/spark/pull/18156
Although I agree that 3.1415 should round to 3.141 in both cases, the value
of 3.1415f is not quite the same as 3.1415. It's actually something like
3.1414... The behavior is correct,
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18118
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/77578/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18118
**[Test build #77578 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/77578/testReport)**
for PR 18118 at commit
Github user liyichao commented on a diff in the pull request:
https://github.com/apache/spark/pull/18129#discussion_r119309080
--- Diff:
resource-managers/yarn/src/test/scala/org/apache/spark/deploy/yarn/ClientSuite.scala
---
@@ -116,15 +116,16 @@ class ClientSuite extends
Github user guoxiaolongzte commented on the issue:
https://github.com/apache/spark/pull/18015
@srowen
SQL ui is really different from other ui. In the follow-up version, I will
strive to improve the function of SQL ui.
---
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/18108
It won't pass automated dependency checks. The tests are not relevant here.
You need to investigate what has changed and what the implication is for Hadoop
envs without this change
---
If your
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18159
**[Test build #77584 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/77584/testReport)**
for PR 18159 at commit
GitHub user viirya opened a pull request:
https://github.com/apache/spark/pull/18159
[SPARK-20703][SQL][WIP] Associate metrics with data writes onto
DataFrameWriter operations
## What changes were proposed in this pull request?
Right now in the UI, after SPARK-20213, we
Github user zuotingbing commented on a diff in the pull request:
https://github.com/apache/spark/pull/18158#discussion_r119302580
--- Diff: core/src/test/scala/org/apache/spark/util/UtilsSuite.scala ---
@@ -473,7 +474,7 @@ class UtilsSuite extends SparkFunSuite with
Github user ueshin commented on a diff in the pull request:
https://github.com/apache/spark/pull/17617#discussion_r119301228
--- Diff: core/src/main/scala/org/apache/spark/deploy/SparkHadoopUtil.scala
---
@@ -21,8 +21,10 @@ import java.io.IOException
import
Github user liu-zhaokun commented on the issue:
https://github.com/apache/spark/pull/18108
@srowen
I think you can test and verify your points via SparkQA's 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
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18158
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/18108
@liu-zhaokun that doesn't address any of my points here
---
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
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/18158#discussion_r119298616
--- Diff: core/src/test/scala/org/apache/spark/util/UtilsSuite.scala ---
@@ -473,7 +474,7 @@ class UtilsSuite extends SparkFunSuite with
GitHub user zuotingbing opened a pull request:
https://github.com/apache/spark/pull/18158
Lack of the most important case about the test of resolveURI in UtilsSuite,
and add it as needed.
## What changes were proposed in this pull request?
add the most important case
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/18015
Yes I understand that, but I don't think the reasoning is as compelling
here, and the style is a bit different.
---
If your project is set up for it, you can reply to this email and have your
reply
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18153
**[Test build #77583 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/77583/testReport)**
for PR 18153 at commit
Github user wangyum commented on the issue:
https://github.com/apache/spark/pull/18153
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 MLnick commented on the issue:
https://github.com/apache/spark/pull/18151
Good catch. Agree with @sethah comment about adding a test case, otherwise
LGTM
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17617
**[Test build #77581 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/77581/testReport)**
for PR 17617 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17113
**[Test build #77582 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/77582/testReport)**
for PR 17113 at commit
Github user jerryshao commented on the issue:
https://github.com/apache/spark/pull/17113
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 SparkQA commented on the issue:
https://github.com/apache/spark/pull/18155
**[Test build #77580 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/77580/testReport)**
for PR 18155 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18155
**[Test build #77579 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/77579/testReport)**
for PR 18155 at commit
Github user ueshin commented on the issue:
https://github.com/apache/spark/pull/18155
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 actuaryzhang commented on a diff in the pull request:
https://github.com/apache/spark/pull/18140#discussion_r119285081
--- Diff: R/pkg/inst/tests/testthat/test_mllib_regression.R ---
@@ -379,6 +379,49 @@ test_that("glm save/load", {
unlink(modelPath)
})
Github user vivekdixit05 commented on the issue:
https://github.com/apache/spark/pull/14377
While reading.
---
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 SparkQA commented on the issue:
https://github.com/apache/spark/pull/18118
**[Test build #77578 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/77578/testReport)**
for PR 18118 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18155
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/18155
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/77573/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17113
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/77575/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18153
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/18153
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/77576/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17113
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/18157
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/18157
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/77577/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18157
**[Test build #77577 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/77577/testReport)**
for PR 18157 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18151
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/77574/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18151
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/18151
**[Test build #77574 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/77574/testReport)**
for PR 18151 at commit
GitHub user wangyum opened a pull request:
https://github.com/apache/spark/pull/18157
[MINOR][SQL] Fix a few function description error.
## What changes were proposed in this pull request?
Fix a few function description error.
## How was this patch tested?
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18156
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 10110346 opened a pull request:
https://github.com/apache/spark/pull/18156
[SPARK-20933][SQL]when the input parameter is float typeï¼the âround â
or âbroundâ function can't work well
## What changes were proposed in this pull request?
spark-sql>select
Github user liu-zhaokun commented on the issue:
https://github.com/apache/spark/pull/18108
@srowen
I have tested it in my cluster with modify the version of curator,spark
works normally,and the problem I encountered was resolved.
---
If your project is set up for it, you can
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18151
**[Test build #3769 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3769/testReport)**
for PR 18151 at commit
Github user guoxiaolongzte commented on the issue:
https://github.com/apache/spark/pull/18015
@srowen
I think the style exists to provide links that jump to Running Queries or
Completed Queries because it may be well below the fold if there are many
workers.Job page, stage page,
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/18015
I don't think those links are worth the vertical space they chew up
---
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
301 - 400 of 406 matches
Mail list logo
