Github user iamhumanbeing commented on the issue:
https://github.com/apache/spark/pull/19037
ok. I will close 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 feature
enabled and
Github user iamhumanbeing closed the pull request at:
https://github.com/apache/spark/pull/19037
---
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
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/19049
When would the history server receive events from clusters with different
resource managers?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/19029
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/81118/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/19029
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/19029
**[Test build #81118 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/81118/testReport)**
for PR 19029 at commit
[`c24292c`](https://github.com/apache/spark/commit/c
Github user guoxiaolongzte commented on the issue:
https://github.com/apache/spark/pull/19049
Sorryï¼I do not understand what you mean.
---
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/19049
This still isn't addressing the point: when would they not _all_ be YARN?
---
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 proje
Github user guoxiaolongzte commented on the issue:
https://github.com/apache/spark/pull/19049
For example, I would like to view some of the applications of the resource
schedule of yarn, I can sort the 'master' column.
---
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/19049
What does knowing the resource scheduler help? but my point is, it's
already known in general.
A history server most certainly collects history from different users'
apps, but not from different
Github user guoxiaolongzte commented on the issue:
https://github.com/apache/spark/pull/19049
1.It is more convenient for the observer to more easily know the resource
scheduling mode of the current spark application.
2.For the 'Spark User' column. It would be identical in alm
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/18488
---
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 ena
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/18488
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 i
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/19051
**[Test build #81120 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/81120/testReport)**
for PR 19051 at commit
[`29fd7d7`](https://github.com/apache/spark/commit/29
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/19051#discussion_r135190132
--- Diff:
mllib/src/test/scala/org/apache/spark/ml/tuning/CrossValidatorSuite.scala ---
@@ -187,14 +187,13 @@ class CrossValidatorSuite
cv2.getEstim
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/19051#discussion_r135190085
--- Diff:
common/kvstore/src/main/java/org/apache/spark/util/kvstore/KVStoreIterator.java
---
@@ -31,7 +32,7 @@
*
*/
@Private
-public
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/19051#discussion_r135190194
--- Diff: pom.xml ---
@@ -2058,7 +2058,7 @@
${java.version}
-target
${java.version}
-
GitHub user srowen opened a pull request:
https://github.com/apache/spark/pull/19051
[MINOR][BUILD] Fix build warnings and Java lint errors
## What changes were proposed in this pull request?
Fix build warnings and Java lint errors. This just helps a bit in
evaluating (new)
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/19049
What's the value of this column? In just about all cases it will have the
same value in every row, like 'yarn'. Even if not, why is it useful?
---
If your project is set up for it, you can reply to
Github user guoxiaolongzte commented on the issue:
https://github.com/apache/spark/pull/19049
Sorry, I did not understand what you meant.
---
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 SparkQA commented on the issue:
https://github.com/apache/spark/pull/15435
**[Test build #81119 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/81119/testReport)**
for PR 15435 at commit
[`1395de2`](https://github.com/apache/spark/commit/13
Github user WeichenXu123 commented on the issue:
https://github.com/apache/spark/pull/15435
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 w
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/19049
Why? It would be identical in almost all use cases.
---
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/19037
Same, why do you think the test can or should be more specific? There is no
motivation
---
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 AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18991
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/18991
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/81114/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18991
**[Test build #81114 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/81114/testReport)**
for PR 18991 at commit
[`2bc2b17`](https://github.com/apache/spark/commit/2
Github user ScrapCodes commented on a diff in the pull request:
https://github.com/apache/spark/pull/17357#discussion_r135187410
--- Diff:
core/src/main/scala/org/apache/spark/deploy/rest/StandaloneRestServer.scala ---
@@ -139,7 +139,9 @@ private[rest] class StandaloneSubmitRequest
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/19029
**[Test build #81118 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/81118/testReport)**
for PR 19029 at commit
[`c24292c`](https://github.com/apache/spark/commit/c2
Github user viirya commented on the issue:
https://github.com/apache/spark/pull/18956
`RewritePredicateSubquery` fails structural integrity check because it can
produce `Join` with conflicting attributes in its left and right plans.
I submitted #19050 to fix it.
---
If your
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/19050
**[Test build #81117 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/81117/testReport)**
for PR 19050 at commit
[`edb6271`](https://github.com/apache/spark/commit/ed
GitHub user viirya opened a pull request:
https://github.com/apache/spark/pull/19050
[SPARK-21835][SQL][WIP] RewritePredicateSubquery should not produce
unresolved query plans
## What changes were proposed in this pull request?
`RewritePredicateSubquery` rewrites correlated
Github user WeichenXu123 commented on a diff in the pull request:
https://github.com/apache/spark/pull/19029#discussion_r135186430
--- Diff: mllib/src/main/scala/org/apache/spark/ml/stat/Summarizer.scala ---
@@ -438,6 +438,10 @@ private[ml] object SummaryBuilderImpl extends Logging
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/19049
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 guoxiaolongzte opened a pull request:
https://github.com/apache/spark/pull/19049
[WEB-UI]Add the 'master' column to identify the type of resource management
for the spark job, in the history server web ui.
## What changes were proposed in this pull request?
Add the '
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/19044
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/19044
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/81113/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/19044
**[Test build #81113 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/81113/testReport)**
for PR 19044 at commit
[`e042621`](https://github.com/apache/spark/commit/e
Github user caneGuy commented on the issue:
https://github.com/apache/spark/pull/18730
@cloud-fan can we retest this?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
enable
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18730
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/81112/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18730
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 SparkQA commented on the issue:
https://github.com/apache/spark/pull/18730
**[Test build #81112 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/81112/testReport)**
for PR 18730 at commit
[`14ca824`](https://github.com/apache/spark/commit/1
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15435
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/15435
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/8/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/19048
**[Test build #81116 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/81116/testReport)**
for PR 19048 at commit
[`e000db3`](https://github.com/apache/spark/commit/e0
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15435
**[Test build #8 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/8/testReport)**
for PR 15435 at commit
[`1395de2`](https://github.com/apache/spark/commit/1
Github user sitalkedia commented on the issue:
https://github.com/apache/spark/pull/19048
cc - @markhamstra , @sameeragarwal, @rxin, @vanzin,
---
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 dongjoon-hyun commented on the issue:
https://github.com/apache/spark/pull/18953
Hi, @cloud-fan .
Could you review this again when you have sometime?
---
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 AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18966
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/18966
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/81109/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18966
**[Test build #81109 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/81109/testReport)**
for PR 18966 at commit
[`ea9fea4`](https://github.com/apache/spark/commit/e
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17886
**[Test build #81115 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/81115/testReport)**
for PR 17886 at commit
[`e752d42`](https://github.com/apache/spark/commit/e
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17886
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/81115/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17886
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/19048
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/81110/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/19048
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 SparkQA commented on the issue:
https://github.com/apache/spark/pull/19048
**[Test build #81110 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/81110/testReport)**
for PR 19048 at commit
[`e30bbac`](https://github.com/apache/spark/commit/e
Github user dongjoon-hyun commented on the issue:
https://github.com/apache/spark/pull/18991
Hi, @cloud-fan, @gatorsmile , @sameeragarwal , @rxin , @mridulm .
Could you reivew this one liner PR about ORC PPD configuration?
---
If your project is set up for it, you can reply to thi
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18991
**[Test build #81114 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/81114/testReport)**
for PR 18991 at commit
[`2bc2b17`](https://github.com/apache/spark/commit/2b
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17886
**[Test build #81115 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/81115/testReport)**
for PR 17886 at commit
[`e752d42`](https://github.com/apache/spark/commit/e7
Github user dongjoon-hyun commented on the issue:
https://github.com/apache/spark/pull/18991
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/19044
**[Test build #81113 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/81113/testReport)**
for PR 19044 at commit
[`e042621`](https://github.com/apache/spark/commit/e0
Github user jerryshao commented on the issue:
https://github.com/apache/spark/pull/19034
Agree with @vanzin , if you really want to fix this issue I think you
should find out the root cause and fix the code in Spark.
---
If your project is set up for it, you can reply to this email a
Github user dongjoon-hyun commented on the issue:
https://github.com/apache/spark/pull/19044
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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/18315
---
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 ena
Github user yanboliang commented on the issue:
https://github.com/apache/spark/pull/18315
Merged into master. Thanks for all.
---
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
enab
Github user yanboliang commented on a diff in the pull request:
https://github.com/apache/spark/pull/18315#discussion_r135172322
--- Diff:
mllib/src/test/scala/org/apache/spark/ml/optim/aggregator/HingeAggregatorSuite.scala
---
@@ -0,0 +1,150 @@
+/*
+ * Licensed to the Apa
Github user jerryshao commented on the issue:
https://github.com/apache/spark/pull/19039
The changes you made in `BlacklistTracker` seems break the design purpose
of backlist. The blacklist in Spark as well as in MR/TEZ assumes bad
nodes/executors will be back to normal in several hou
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18730
**[Test build #81112 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/81112/testReport)**
for PR 18730 at commit
[`14ca824`](https://github.com/apache/spark/commit/14
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/19044
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/81107/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/19044
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 SparkQA commented on the issue:
https://github.com/apache/spark/pull/19044
**[Test build #81107 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/81107/testReport)**
for PR 19044 at commit
[`e042621`](https://github.com/apache/spark/commit/e
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15435
**[Test build #8 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/8/testReport)**
for PR 15435 at commit
[`1395de2`](https://github.com/apache/spark/commit/13
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/19046
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/19046
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/81108/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/19046
**[Test build #81108 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/81108/testReport)**
for PR 19046 at commit
[`03477f5`](https://github.com/apache/spark/commit/0
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/19048
**[Test build #81110 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/81110/testReport)**
for PR 19048 at commit
[`e30bbac`](https://github.com/apache/spark/commit/e3
Github user dongjoon-hyun commented on the issue:
https://github.com/apache/spark/pull/19044
Thank you for review, @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
e
GitHub user sitalkedia opened a pull request:
https://github.com/apache/spark/pull/19048
[SPARK-21834] Incorrect executor request in case of dynamic allocation
## What changes were proposed in this pull request?
killExecutor api currently does not allow killing an executor w
Github user maropu commented on the issue:
https://github.com/apache/spark/pull/19031
ping
---
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 SparkQA commented on the issue:
https://github.com/apache/spark/pull/18966
**[Test build #81109 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/81109/testReport)**
for PR 18966 at commit
[`ea9fea4`](https://github.com/apache/spark/commit/ea
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/16422
ping @wzhfy
---
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 i
Github user kiszk commented on a diff in the pull request:
https://github.com/apache/spark/pull/18966#discussion_r135164815
--- Diff:
sql/core/src/test/scala/org/apache/spark/sql/execution/benchmark/BenchmarkWideTable.scala
---
@@ -42,12 +42,16 @@ class BenchmarkWideTable extends
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/19046
**[Test build #81108 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/81108/testReport)**
for PR 19046 at commit
[`03477f5`](https://github.com/apache/spark/commit/03
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/19044
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 fe
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/19044
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/81106/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/19044
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/19044
**[Test build #81106 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/81106/testReport)**
for PR 19044 at commit
[`bc906c8`](https://github.com/apache/spark/commit/b
Github user iamhumanbeing commented on the issue:
https://github.com/apache/spark/pull/19037
@srowen How about
"assert(exchanges.map(_.outputPartitioning.numPartitions).sorted === List(2, 2,
2, 3))"?
---
If your project is set up for it, you can reply to this email and have your
re
Github user cloud-fan closed the pull request at:
https://github.com/apache/spark/pull/19040
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/19045
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/81103/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/19045
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/19045
**[Test build #81103 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/81103/testReport)**
for PR 19045 at commit
[`65a29c1`](https://github.com/apache/spark/commit/6
Github user kiszk commented on the issue:
https://github.com/apache/spark/pull/18704
@cloud-fan could you please review this again?
---
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 featur
Github user ArtRand commented on the issue:
https://github.com/apache/spark/pull/18837
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 wis
Github user viirya commented on the issue:
https://github.com/apache/spark/pull/18956
Seems there are other issues caused by `RewritePredicateSubquery` rule.
I'll investigate and fix it.
---
If your project is set up for it, you can reply to this email and have your
reply appear on G
Github user dongjoon-hyun commented on a diff in the pull request:
https://github.com/apache/spark/pull/19044#discussion_r135158510
--- Diff:
sql/hive/src/test/scala/org/apache/spark/sql/catalyst/ExpressionSQLBuilderSuite.scala
---
@@ -19,12 +19,28 @@ package org.apache.spark.sql.
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/19044
**[Test build #81107 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/81107/testReport)**
for PR 19044 at commit
[`e042621`](https://github.com/apache/spark/commit/e0
Github user dongjoon-hyun commented on a diff in the pull request:
https://github.com/apache/spark/pull/19044#discussion_r135157926
--- Diff:
sql/hive/src/test/scala/org/apache/spark/sql/catalyst/ExpressionSQLBuilderSuite.scala
---
@@ -19,12 +19,28 @@ package org.apache.spark.sql.
Github user gatorsmile commented on a diff in the pull request:
https://github.com/apache/spark/pull/18966#discussion_r135157982
--- Diff:
sql/core/src/test/scala/org/apache/spark/sql/execution/benchmark/BenchmarkWideTable.scala
---
@@ -42,12 +42,16 @@ class BenchmarkWideTable ext
1 - 100 of 395 matches
Mail list logo
