Github user cloud-fan commented on the pull request:
https://github.com/apache/spark/pull/12599#issuecomment-213272475
@viirya , yea you are right, `ObjectConsumer` may also produce objects, so
we should implement `statistic` in `SerializeFromObject`.
@gatorsmile I may
Github user HyukjinKwon commented on a diff in the pull request:
https://github.com/apache/spark/pull/12598#discussion_r60693434
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/joins/HashedRelation.scala
---
@@ -324,8 +324,8 @@ private[joins] object
Github user HyukjinKwon commented on a diff in the pull request:
https://github.com/apache/spark/pull/12598#discussion_r60693402
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/joins/HashedRelation.scala
---
@@ -325,7 +325,7 @@ private[joins] object
Github user gatorsmile commented on the pull request:
https://github.com/apache/spark/pull/12599#issuecomment-213269638
The problem is the parent node calls the defaultSize of its child's output.
```scala
val childRowSize = child.output.map(_.dataType.defaultSize).sum
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12560#issuecomment-213268198
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12560#issuecomment-213268088
**[Test build #56655 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56655/consoleFull)**
for PR 12560 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12560#issuecomment-213268202
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user gatorsmile commented on the pull request:
https://github.com/apache/spark/pull/12599#issuecomment-213267994
@viirya Nope. Actually, I did that before. It does not work. The issue is
its parent node's statistics calculation triggers the exception.
---
If your project is
Github user viirya commented on the pull request:
https://github.com/apache/spark/pull/12599#issuecomment-213265799
@gatorsmile Looks at the `SerializeFromObject` in your plan. If we
implement `statistics` in it, we can skip estimating size of `MapGroups` which
produces domain
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12344#issuecomment-213266271
**[Test build #56658 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56658/consoleFull)**
for PR 12344 at commit
Github user gatorsmile commented on the pull request:
https://github.com/apache/spark/pull/12599#issuecomment-213265498
When we calculating the statistics of `Filter`, we hit the issue caused by
the `UnaryNode`'s default statistics calculation, right?
---
If your project is set up
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12344#issuecomment-213265119
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12344#issuecomment-213265121
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12344#issuecomment-213265117
**[Test build #56657 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56657/consoleFull)**
for PR 12344 at commit
Github user gatorsmile commented on the pull request:
https://github.com/apache/spark/pull/12599#issuecomment-213265063
```
== Optimized Logical Plan ==
Project [user#7,recommendations#48 AS prediction#77,actual#65 AS label#78]
+- Join Inner, Some((user#7 = id#64))
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12560#issuecomment-213264908
**[Test build #56655 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56655/consoleFull)**
for PR 12560 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12344#issuecomment-213264912
**[Test build #56657 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56657/consoleFull)**
for PR 12344 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12425#issuecomment-213264910
**[Test build #56656 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56656/consoleFull)**
for PR 12425 at commit
Github user viirya commented on the pull request:
https://github.com/apache/spark/pull/12599#issuecomment-213264884
@cloud-fan Is there guarantee that an `ObjectConsumer` can't produce domain
object? If no, I think it is safer to implement `statistics` in
`SerializeFromObject`,
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12425#issuecomment-213264628
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12425#issuecomment-213264623
**[Test build #56654 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56654/consoleFull)**
for PR 12425 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12425#issuecomment-213264631
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user viirya commented on the pull request:
https://github.com/apache/spark/pull/12599#issuecomment-213264562
Yea I see.
---
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 HyukjinKwon commented on the pull request:
https://github.com/apache/spark/pull/12494#issuecomment-213264603
Filed in [SPARK-14839](https://issues.apache.org/jira/browse/SPARK-14839).
I might be able to give a shot **if** nobody gives a try.
---
If your project is set up
Github user davies commented on the pull request:
https://github.com/apache/spark/pull/12425#issuecomment-213264516
@zsxwing Addressed you comments.
---
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
Github user wangmiao1981 commented on the pull request:
https://github.com/apache/spark/pull/12560#issuecomment-213264393
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12568#issuecomment-213264162
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user cloud-fan commented on the pull request:
https://github.com/apache/spark/pull/12599#issuecomment-213264156
The object operators are really special, it breaks the contract that
operator will always produce unsafe rows, so their usage is quite limited.
Generally speaking,
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12568#issuecomment-213264159
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12425#issuecomment-213263958
**[Test build #56654 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56654/consoleFull)**
for PR 12425 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12568#issuecomment-213263681
**[Test build #56641 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56641/consoleFull)**
for PR 12568 at commit
Github user viirya commented on the pull request:
https://github.com/apache/spark/pull/12599#issuecomment-213261995
Let me try it...
---
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 viirya commented on the pull request:
https://github.com/apache/spark/pull/12599#issuecomment-213261576
@cloud-fan Sounds good.
---
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 gatorsmile commented on the pull request:
https://github.com/apache/spark/pull/12599#issuecomment-213260014
We need to change the implementation of `UnaryNode `'s the default
statistics calculation. However, the other node types that do not use the
default method still
Github user gatorsmile commented on the pull request:
https://github.com/apache/spark/pull/12599#issuecomment-213259525
@cloud-fan That does not help. The parent `UnaryNode` can be any type. We
will face this issue when its child is `SerializeFromObject `
---
If your project is set
Github user gatorsmile commented on a diff in the pull request:
https://github.com/apache/spark/pull/12599#discussion_r60691895
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/SparkStrategies.scala ---
@@ -82,7 +82,10 @@ private[sql] abstract class SparkStrategies
Github user cloud-fan commented on the pull request:
https://github.com/apache/spark/pull/12599#issuecomment-213259121
After think about it, it is better to implement `statistics` in
`SerializeFromObject`?
---
If your project is set up for it, you can reply to this email and have
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12588#issuecomment-213258484
**[Test build #2855 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/2855/consoleFull)**
for PR 12588 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12583#issuecomment-213258488
**[Test build #56653 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56653/consoleFull)**
for PR 12583 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12588#issuecomment-213258485
**[Test build #56652 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56652/consoleFull)**
for PR 12588 at commit
Github user viirya commented on a diff in the pull request:
https://github.com/apache/spark/pull/12599#discussion_r60691766
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/SparkStrategies.scala ---
@@ -82,7 +82,10 @@ private[sql] abstract class SparkStrategies
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12583#issuecomment-213258112
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12583#issuecomment-213258111
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12583#issuecomment-213258107
**[Test build #56651 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56651/consoleFull)**
for PR 12583 at commit
Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/12599#discussion_r60691640
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/SparkStrategies.scala ---
@@ -82,7 +82,10 @@ private[sql] abstract class SparkStrategies
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12599#issuecomment-213257892
**[Test build #56650 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56650/consoleFull)**
for PR 12599 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12583#issuecomment-213257903
**[Test build #56651 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56651/consoleFull)**
for PR 12583 at commit
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/8216
---
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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/12557
---
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 rxin commented on the pull request:
https://github.com/apache/spark/pull/12600#issuecomment-213257569
Is there a way to create a test case?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12600#issuecomment-213257260
**[Test build #56648 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56648/consoleFull)**
for PR 12600 at commit
Github user yzhou2001 commented on the pull request:
https://github.com/apache/spark/pull/12598#issuecomment-213257305
cc @rajeshbalamohan
---
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 viirya commented on the pull request:
https://github.com/apache/spark/pull/12599#issuecomment-213257282
@cloud-fan Just added.
---
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 davies commented on the pull request:
https://github.com/apache/spark/pull/12557#issuecomment-213257298
Merging this into 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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12081#issuecomment-213257176
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12494#issuecomment-213257166
**[Test build #56649 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56649/consoleFull)**
for PR 12494 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12081#issuecomment-213257173
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
Github user cloud-fan commented on the pull request:
https://github.com/apache/spark/pull/12599#issuecomment-213257114
Can you construct a query that can trigger this bug?
---
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12081#issuecomment-213257067
**[Test build #56643 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56643/consoleFull)**
for PR 12081 at commit
Github user davies commented on the pull request:
https://github.com/apache/spark/pull/12600#issuecomment-213257084
cc @zsxwing @rxin
---
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 davies opened a pull request:
https://github.com/apache/spark/pull/12600
[SPARK-14791] [SQL] fix risk condition between broadcast and subquery
## What changes were proposed in this pull request?
SparkPlan.prepare() could be called in different threads
Github user viirya commented on the pull request:
https://github.com/apache/spark/pull/12494#issuecomment-213256865
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
Github user viirya commented on the pull request:
https://github.com/apache/spark/pull/12494#issuecomment-213256768
@HyukjinKwon yea. I have no problem with it.
---
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 viirya commented on a diff in the pull request:
https://github.com/apache/spark/pull/12599#discussion_r60691109
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/SparkStrategies.scala ---
@@ -82,7 +82,10 @@ private[sql] abstract class SparkStrategies
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12573#issuecomment-213255245
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/12599#discussion_r60690868
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/SparkStrategies.scala ---
@@ -82,7 +82,10 @@ private[sql] abstract class SparkStrategies
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12573#issuecomment-213255240
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12573#issuecomment-213254800
**[Test build #56646 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56646/consoleFull)**
for PR 12573 at commit
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/12527
---
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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/12594
---
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 yzhou2001 commented on the pull request:
https://github.com/apache/spark/pull/12598#issuecomment-213253503
@HyukjinKwon thanks for comments. will make the change soon
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/12594#issuecomment-213253591
Merging in master.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this
Github user davies commented on the pull request:
https://github.com/apache/spark/pull/12527#issuecomment-213253318
Merging this into 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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12527#issuecomment-213252687
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12527#issuecomment-213252688
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user cloud-fan commented on the pull request:
https://github.com/apache/spark/pull/12559#issuecomment-213252594
Does it work in whole stage codegen?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12527#issuecomment-213252532
**[Test build #56639 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56639/consoleFull)**
for PR 12527 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12599#issuecomment-213252296
**[Test build #56647 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56647/consoleFull)**
for PR 12599 at commit
GitHub user viirya opened a pull request:
https://github.com/apache/spark/pull/12599
[SPARK-14838][SQL] Skip automatically broadcast a plan when it contains
ObjectProducer
## What changes were proposed in this pull request?
In `SparkStrategies`, `CanBroadcast` will
Github user tanwanirahul closed the pull request at:
https://github.com/apache/spark/pull/11219
---
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 tanwanirahul commented on the pull request:
https://github.com/apache/spark/pull/11219#issuecomment-213249792
@jkbradley Make sense. 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
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/12440
---
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 davies commented on the pull request:
https://github.com/apache/spark/pull/12440#issuecomment-213246941
LGTM,
Merging this into 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
Github user davies commented on the pull request:
https://github.com/apache/spark/pull/12494#issuecomment-213245952
@HyukjinKwon Sounds good to me
---
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12596#issuecomment-213245798
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12596#issuecomment-213245800
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12596#issuecomment-213245748
**[Test build #56645 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56645/consoleFull)**
for PR 12596 at commit
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/12559
---
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 HyukjinKwon closed the pull request at:
https://github.com/apache/spark/pull/10502
---
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 HyukjinKwon commented on the pull request:
https://github.com/apache/spark/pull/10502#issuecomment-213244434
Let me close this for now. Please let me know although this is closed. I
will reopen this when I start to work on this again.
---
If your project is set up for
Github user davies commented on the pull request:
https://github.com/apache/spark/pull/12559#issuecomment-213243926
Merging this into 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
Github user HyukjinKwon commented on the pull request:
https://github.com/apache/spark/pull/11201#issuecomment-213243682
ping @jaceklaskowski
---
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 HyukjinKwon commented on the pull request:
https://github.com/apache/spark/pull/11219#issuecomment-213243550
@tanwanirahul Could you fill up the PR description with the purpose please?
---
If your project is set up for it, you can reply to this email and have your
reply
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12573#issuecomment-213243054
**[Test build #56646 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56646/consoleFull)**
for PR 12573 at commit
Github user HyukjinKwon commented on the pull request:
https://github.com/apache/spark/pull/11457#issuecomment-213243006
I am closing this but it would be great to let me know if you have a new PR
for this.
---
If your project is set up for it, you can reply to this email and have
Github user HyukjinKwon closed the pull request at:
https://github.com/apache/spark/pull/11457
---
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 HyukjinKwon commented on the pull request:
https://github.com/apache/spark/pull/11724#issuecomment-213242625
@rxin I am willing to close this one if you are not sure of this one.
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user ueshin commented on the pull request:
https://github.com/apache/spark/pull/12559#issuecomment-213241810
@rxin I updated the pr description.
---
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12583#issuecomment-213236005
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12583#issuecomment-213235543
**[Test build #56636 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56636/consoleFull)**
for PR 12583 at commit
1 - 100 of 1263 matches
Mail list logo
