Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16867
**[Test build #74640 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/74640/testReport)**
for PR 16867 at commit
[`104e867`](https://github.com/apache/spark/commit/1
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16867
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
e
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16867
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/74640/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17308
**[Test build #74646 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/74646/testReport)**
for PR 17308 at commit
[`830d76d`](https://github.com/apache/spark/commit/83
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17308
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
e
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17308
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/74644/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17287
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/74643/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17251
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/74641/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17251
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
e
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17287
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
e
Github user windpiger commented on the issue:
https://github.com/apache/spark/pull/17287
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 wishes so,
Github user ouyangxiaochen closed the pull request at:
https://github.com/apache/spark/pull/17270
---
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 featur
GitHub user jianran opened a pull request:
https://github.com/apache/spark/pull/17309
same rdd rule testcase
## What changes were proposed in this pull request?
I improvise and change the testcase because rdd_0_2 didn't removed is
because of same rdd-rule not because of rd
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17309
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 feat
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17070
**[Test build #74648 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/74648/testReport)**
for PR 17070 at commit
[`32c0017`](https://github.com/apache/spark/commit/32
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17287
**[Test build #74647 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/74647/testReport)**
for PR 17287 at commit
[`d82e8ed`](https://github.com/apache/spark/commit/d8
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16867
**[Test build #74649 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/74649/testReport)**
for PR 16867 at commit
[`2518a95`](https://github.com/apache/spark/commit/25
Github user morenn520 commented on the issue:
https://github.com/apache/spark/pull/17238
Thanks @tgravescs , we has used a dynamic topology discovery script to
avoid this problem. Since tez and mr donât do this, maybe spark could not fix
this problem.
---
If your project is set up
Github user lw-lin commented on a diff in the pull request:
https://github.com/apache/spark/pull/17070#discussion_r106352628
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/streaming/HDFSMetadataLog.scala
---
@@ -195,6 +195,11 @@ class HDFSMetadataLog[T <: AnyRef
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/16672
To backport https://github.com/apache/spark/pull/17097, we need to backport
multiple PRs. This is one of it.
@windpiger Could you please submit a PR to backport it to Spark 2.1?
---
If
Github user MLnick commented on the issue:
https://github.com/apache/spark/pull/11601
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 wishe
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17242
**[Test build #74650 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/74650/testReport)**
for PR 17242 at commit
[`b1a0641`](https://github.com/apache/spark/commit/b1
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/11601
**[Test build #74651 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/74651/testReport)**
for PR 11601 at commit
[`c67afc1`](https://github.com/apache/spark/commit/c6
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16626
**[Test build #74652 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/74652/testReport)**
for PR 16626 at commit
[`211287e`](https://github.com/apache/spark/commit/21
Github user wzhfy commented on a diff in the pull request:
https://github.com/apache/spark/pull/17286#discussion_r106355108
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/optimizer/CostBasedJoinReorder.scala
---
@@ -128,38 +128,43 @@ case class CostBasedJoinRe
Github user MLnick commented on the issue:
https://github.com/apache/spark/pull/11601
Created [SPARK-19969](https://issues.apache.org/jira/browse/SPARK-19969) to
track doc and examples to be done for 2.2 release. I can help with this if
you're tied up.
---
If your project is set up
Github user wzhfy commented on a diff in the pull request:
https://github.com/apache/spark/pull/17286#discussion_r106357158
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/internal/SQLConf.scala ---
@@ -696,6 +696,13 @@ object SQLConf {
.intConf
.cr
GitHub user HyukjinKwon opened a pull request:
https://github.com/apache/spark/pull/17310
[SPARK-18579][SQL] Use ignoreLeadingWhiteSpace and ignoreTrailingWhiteSpace
options in CSV writing
## What changes were proposed in this pull request?
This PR proposes to support _not_
Github user MLnick commented on the issue:
https://github.com/apache/spark/pull/17296
hmm I would prefer to test it though I do get it's pretty tricky to do
generically. I don't think training a tiny model on a couple data points will
add too much overhead.
---
If your project is se
Github user HyukjinKwon commented on a diff in the pull request:
https://github.com/apache/spark/pull/17310#discussion_r106357631
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/datasources/csv/CSVOptions.scala
---
@@ -92,8 +92,13 @@ class CSVOptions(
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17310
**[Test build #74653 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/74653/testReport)**
for PR 17310 at commit
[`a16f0c5`](https://github.com/apache/spark/commit/a1
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17242
**[Test build #74650 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/74650/testReport)**
for PR 17242 at commit
[`b1a0641`](https://github.com/apache/spark/commit/b
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17242
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/74650/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17242
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
e
Github user felixcheung commented on the issue:
https://github.com/apache/spark/pull/16596
@shivaram what do you think about
https://github.com/apache/spark/pull/16596#issuecomment-286015752?
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user felixcheung commented on a diff in the pull request:
https://github.com/apache/spark/pull/16330#discussion_r106359526
--- Diff: core/src/main/scala/org/apache/spark/api/r/RRDD.scala ---
@@ -127,6 +127,13 @@ private[r] object RRDD {
sparkConf.setExecutorEnv(nam
Github user dongjoon-hyun commented on the issue:
https://github.com/apache/spark/pull/17251
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 wishes
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/17309
See http://spark.apache.org/contributing.html
I'm not clear this adds any value?
---
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 melin commented on the issue:
https://github.com/apache/spark/pull/16324
in spark 2.1.0
0: jdbc:hive2://localhost:1> add jar
hdfs:///user/datacompute/datacompute-udf-1.0-
Error: java.net.MalformedURLException: unknown protocol: hdfs
(state=,code=0)
0: jdbc
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17251
**[Test build #74654 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/74654/testReport)**
for PR 17251 at commit
[`c951084`](https://github.com/apache/spark/commit/c9
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/11601
**[Test build #74651 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/74651/testReport)**
for PR 11601 at commit
[`c67afc1`](https://github.com/apache/spark/commit/c
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/11601
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/74651/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/11601
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
e
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/17290
I'd like to merge this as a step towards possibly resolving the problem or
uncovering its root.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/17306
Yes re: JIRA
CC @MLNick or @jkbradley as well
I agree about reusing the cached folds, that's a good point. I think this
is worth considering.
---
If your project is set up for it, you c
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17308
**[Test build #74646 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/74646/testReport)**
for PR 17308 at commit
[`830d76d`](https://github.com/apache/spark/commit/8
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17308
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
e
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17308
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/74646/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16476
**[Test build #74655 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/74655/testReport)**
for PR 16476 at commit
[`fc47e0f`](https://github.com/apache/spark/commit/fc
Github user crackcell commented on a diff in the pull request:
https://github.com/apache/spark/pull/17123#discussion_r106363022
--- Diff: mllib/src/main/scala/org/apache/spark/ml/feature/Bucketizer.scala
---
@@ -105,20 +106,21 @@ final class Bucketizer @Since("1.4.0")
(@Since("1.4
Github user hvanhovell commented on a diff in the pull request:
https://github.com/apache/spark/pull/17244#discussion_r106363391
--- Diff: core/src/main/scala/org/apache/spark/TaskContextImpl.scala ---
@@ -52,62 +63,79 @@ private[spark] class TaskContextImpl(
@volatile privat
Github user gczsjdy commented on the issue:
https://github.com/apache/spark/pull/16476
@cloud-fan I have submitted a new version to support implicit cast.
We determine the implicit cast type in analysis stage, so maybe we won't do
`eval` then, so we can't be 100% intelligent, for e
Github user wzhfy commented on the issue:
https://github.com/apache/spark/pull/17286
Co-existing cross joins (join without a condition) and inner joins make the
reordering procedure cumbersome. On one hand, putting cross join candidates
into memo is not good in terms of search perform
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17286
**[Test build #74656 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/74656/testReport)**
for PR 17286 at commit
[`237ad9d`](https://github.com/apache/spark/commit/23
Github user wzhfy commented on a diff in the pull request:
https://github.com/apache/spark/pull/15363#discussion_r106364472
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/optimizer/CostBasedJoinReorder.scala
---
@@ -51,6 +51,11 @@ case class CostBasedJoinReord
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17070
**[Test build #74648 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/74648/testReport)**
for PR 17070 at commit
[`32c0017`](https://github.com/apache/spark/commit/3
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17070
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
e
GitHub user dongjoon-hyun opened a pull request:
https://github.com/apache/spark/pull/17311
[SPARK-19970][SQL] Table owner should be USER instead of PRINCIPAL in
kerberized clusters
## What changes were proposed in this pull request?
In the kerberized hadoop cluster, when S
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17070
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/74648/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17311
**[Test build #74657 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/74657/testReport)**
for PR 17311 at commit
[`9dfbf82`](https://github.com/apache/spark/commit/9d
Github user dongjoon-hyun commented on the issue:
https://github.com/apache/spark/pull/17311
Hi, @vanzin .
Could you review this PR?
---
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 f
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17287
**[Test build #74647 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/74647/testReport)**
for PR 17287 at commit
[`d82e8ed`](https://github.com/apache/spark/commit/d
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17308
**[Test build #74658 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/74658/testReport)**
for PR 17308 at commit
[`0b5e2e8`](https://github.com/apache/spark/commit/0b
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17287
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
e
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17287
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/74647/
Test PASSed.
---
Github user hvanhovell commented on the issue:
https://github.com/apache/spark/pull/17292
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 wishes so
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16626
**[Test build #74652 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/74652/testReport)**
for PR 16626 at commit
[`211287e`](https://github.com/apache/spark/commit/2
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17268
**[Test build #74660 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/74660/testReport)**
for PR 17268 at commit
[`d76a138`](https://github.com/apache/spark/commit/d7
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17292
**[Test build #74659 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/74659/testReport)**
for PR 17292 at commit
[`72d8230`](https://github.com/apache/spark/commit/72
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16626
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/74652/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16626
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
e
Github user jianran closed the pull request at:
https://github.com/apache/spark/pull/17309
---
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 en
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16867
**[Test build #74649 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/74649/testReport)**
for PR 16867 at commit
[`2518a95`](https://github.com/apache/spark/commit/2
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16867
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/74649/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16867
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
e
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17274
**[Test build #74661 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/74661/testReport)**
for PR 17274 at commit
[`44e6d32`](https://github.com/apache/spark/commit/44
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17311
**[Test build #74657 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/74657/testReport)**
for PR 17311 at commit
[`9dfbf82`](https://github.com/apache/spark/commit/9
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17311
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
e
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17311
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/74657/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17310
**[Test build #74653 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/74653/testReport)**
for PR 17310 at commit
[`a16f0c5`](https://github.com/apache/spark/commit/a
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17310
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
e
GitHub user jinxing64 opened a pull request:
https://github.com/apache/spark/pull/17312
Display num of executors for the stage.
## What changes were proposed in this pull request?
In `StagePage` the total num of executors are not displayed. Since
executorId may not be conse
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17310
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/74653/
Test PASSed.
---
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/17312
No, just putting a number in the UI isn't correct. I am not sure this has
that much value.
This isn't how we manage changes anyway. Please read
http://spark.apache.org/contributing.html
---
If
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17312
**[Test build #74662 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/74662/testReport)**
for PR 17312 at commit
[`f64691c`](https://github.com/apache/spark/commit/f6
Github user jinxing64 commented on the issue:
https://github.com/apache/spark/pull/17312
@srowen
Thanks a lot for quick reply. When we check the reason why a stage ran
today much longer than yesterday, we want to know how many executors are
supplied. We don't want to count the ex
Github user dongjoon-hyun commented on the issue:
https://github.com/apache/spark/pull/17311
Oh, there exists a version issue. Let me fix that.
---
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 jinxing64 closed the pull request at:
https://github.com/apache/spark/pull/17312
---
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/17312
I don't think this is understandable as the executor count. It would also
show the total count of executors include dead ones.
---
If your project is set up for it, you can reply to this email and h
GitHub user jinxing64 reopened a pull request:
https://github.com/apache/spark/pull/17312
[SPARK-19973] Display num of executors for the stage.
## What changes were proposed in this pull request?
In `StagePage` the total num of executors are not displayed. Since
executorId
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17251
**[Test build #74654 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/74654/testReport)**
for PR 17251 at commit
[`c951084`](https://github.com/apache/spark/commit/c
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17251
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
e
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17251
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/74654/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17312
**[Test build #74663 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/74663/testReport)**
for PR 17312 at commit
[`7aa6fe5`](https://github.com/apache/spark/commit/7a
GitHub user jianran opened a pull request:
https://github.com/apache/spark/pull/17313
[SPARK-19974][Block Manager] in-memory LRU for partitions of multiple RDDs
testcase did a get that is no sense
## What changes were proposed in this pull request?
in-memory LRU for partiti
Github user dongjoon-hyun commented on a diff in the pull request:
https://github.com/apache/spark/pull/17311#discussion_r106385533
--- Diff:
sql/hive/src/main/scala/org/apache/spark/sql/hive/client/HiveClientImpl.scala
---
@@ -851,7 +851,7 @@ private[hive] object HiveClientImpl {
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16476
**[Test build #74655 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/74655/testReport)**
for PR 16476 at commit
[`fc47e0f`](https://github.com/apache/spark/commit/f
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17313
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 feat
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16476
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/74655/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16476
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
e
1 - 100 of 591 matches
Mail list logo
