Github user dongjinleekr commented on the issue:
https://github.com/apache/spark/pull/17564
@srowen I just completed the review. I could not find any other typos from
this document. :)
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user gatorsmile commented on a diff in the pull request:
https://github.com/apache/spark/pull/17265#discussion_r111030752
--- Diff:
sql/hive/src/main/scala/org/apache/spark/sql/hive/HiveExternalCatalog.scala ---
@@ -94,7 +96,13 @@ private[spark] class
Github user BryanCutler commented on a diff in the pull request:
https://github.com/apache/spark/pull/16774#discussion_r111025724
--- Diff:
mllib/src/main/scala/org/apache/spark/ml/tuning/ValidatorParams.scala ---
@@ -67,6 +71,39 @@ private[ml] trait ValidatorParams extends
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17610
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/17610
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/75712/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17610
**[Test build #75712 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/75712/testReport)**
for PR 17610 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17546
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/17546
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/75713/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17546
**[Test build #75713 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/75713/testReport)**
for PR 17546 at commit
Github user sameeragarwal commented on a diff in the pull request:
https://github.com/apache/spark/pull/13932#discussion_r111015013
--- Diff:
core/src/test/scala/org/apache/spark/storage/BlockReplicationPolicySuite.scala
---
@@ -68,7 +68,60 @@ class BlockReplicationPolicySuite
Github user tdas commented on the issue:
https://github.com/apache/spark/pull/17609
jenkins test this
---
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 tdas commented on the issue:
https://github.com/apache/spark/pull/17609
That's correct. 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,
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17130
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/75714/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17130
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/17130
**[Test build #75714 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/75714/testReport)**
for PR 17130 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17280
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/17280
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/75715/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17280
**[Test build #75715 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/75715/testReport)**
for PR 17280 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17606
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/75711/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17606
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/17606
**[Test build #75711 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/75711/testReport)**
for PR 17606 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17330
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/17330
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/75710/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17330
**[Test build #75710 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/75710/testReport)**
for PR 17330 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17611
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 SparkQA commented on the issue:
https://github.com/apache/spark/pull/17280
**[Test build #75715 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/75715/testReport)**
for PR 17280 at commit
GitHub user bdwyer2 opened a pull request:
https://github.com/apache/spark/pull/17611
[SPARK-20298][SparkR][MINOR] fixed spelling mistake "charactor"
## What changes were proposed in this pull request?
Fixed spelling of "charactor"
## How was this patch tested?
Github user mgummelt commented on the issue:
https://github.com/apache/spark/pull/17109
@srowen We do appreciate your help with Mesos commits, and generally find
you responsive. I have a habit of pinging you for merges because you seemed to
have stepped in once @andrewor14 stepped
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/17609
CC @tdas to confirm that's correct
---
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
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17130
**[Test build #75714 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/75714/testReport)**
for PR 17130 at commit
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/17109
@yanji84 I have no experience with Mesos and am not, in general, a reviewer
for this code, and don't follow Mesos changes. That's why. I pitch in to help
merge but would appreciate others stepping
Github user zsxwing commented on the issue:
https://github.com/apache/spark/pull/17610
> Isn't it not depending on this being locked in super class methods
invoked in the invocation subtree ?
I don't get it. But I think the stack trace shows why this dead-lock
happens.
---
Github user zsxwing commented on the issue:
https://github.com/apache/spark/pull/17610
@mridulm yeah, I was thinking to just change `stopping` to a AtomicBoolean
flag. However, it changes the semantics a little, e.g., the second `stop` will
return at once when the first `stop` is
Github user map222 commented on the issue:
https://github.com/apache/spark/pull/17469
@HyukjinKwon I have updated the documentation to pass the tests (I didn't
realize the tests actually executed the documented code!). I was able to build
Spark locally, and run `./python/run-tests.py
Github user holdenk commented on the issue:
https://github.com/apache/spark/pull/17222
Thanks for working on this, one thing is the return's from the
`UDFRegistration` functions seem like they won't do much since the functions
they call on the sqlContext don't have returns (and they
Github user holdenk commented on the issue:
https://github.com/apache/spark/pull/16845
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 dbtsai commented on a diff in the pull request:
https://github.com/apache/spark/pull/17606#discussion_r110991443
--- Diff:
sql/catalyst/src/test/scala/org/apache/spark/sql/catalyst/analysis/TypeCoercionSuite.scala
---
@@ -656,14 +656,20 @@ class TypeCoercionSuite
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/16845
---
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 mridulm commented on the issue:
https://github.com/apache/spark/pull/17610
Isn't it not depending on 'this' being locked in super class method ?
If it is not, then why not simply restrict lock to changing of `stopping`
flag (if already set, return, else set and proceed
Github user hhbyyh commented on a diff in the pull request:
https://github.com/apache/spark/pull/17130#discussion_r110990099
--- Diff: examples/src/main/python/ml/fpgrowth_example.py ---
@@ -0,0 +1,48 @@
+#
+# Licensed to the Apache Software Foundation (ASF) under one or
Github user holdenk commented on the issue:
https://github.com/apache/spark/pull/14830
Sure, if you have a chance to rebase & check if any other changes are
needed that would be useful.
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user ioana-delaney commented on a diff in the pull request:
https://github.com/apache/spark/pull/17546#discussion_r110989528
--- Diff:
sql/catalyst/src/test/scala/org/apache/spark/sql/catalyst/optimizer/StarJoinCostBasedReorderSuite.scala
---
@@ -0,0 +1,426 @@
+/*
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17546
**[Test build #75713 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/75713/testReport)**
for PR 17546 at commit
Github user holdenk commented on the issue:
https://github.com/apache/spark/pull/17605
LGTM thanks for adding this.
---
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 ioana-delaney commented on a diff in the pull request:
https://github.com/apache/spark/pull/17546#discussion_r110988847
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/optimizer/StarSchemaDetection.scala
---
@@ -76,7 +76,7 @@ case class
Github user ioana-delaney commented on a diff in the pull request:
https://github.com/apache/spark/pull/17546#discussion_r110987936
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/optimizer/CostBasedJoinReorder.scala
---
@@ -218,28 +220,48 @@ object
Github user ioana-delaney commented on a diff in the pull request:
https://github.com/apache/spark/pull/17546#discussion_r110987408
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/optimizer/CostBasedJoinReorder.scala
---
@@ -327,3 +349,110 @@ object
Github user ioana-delaney commented on a diff in the pull request:
https://github.com/apache/spark/pull/17546#discussion_r110987294
--- Diff:
sql/catalyst/src/test/scala/org/apache/spark/sql/catalyst/optimizer/StarJoinCostBasedReorderSuite.scala
---
@@ -0,0 +1,428 @@
+/*
Github user ioana-delaney commented on a diff in the pull request:
https://github.com/apache/spark/pull/17546#discussion_r110987218
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/optimizer/CostBasedJoinReorder.scala
---
@@ -218,28 +220,48 @@ object
Github user BryanCutler commented on a diff in the pull request:
https://github.com/apache/spark/pull/16774#discussion_r110986801
--- Diff:
mllib/src/main/scala/org/apache/spark/ml/tuning/ValidatorParams.scala ---
@@ -67,6 +71,39 @@ private[ml] trait ValidatorParams extends
Github user zsxwing commented on the issue:
https://github.com/apache/spark/pull/17463
Could you close this one, please? I submitted #17610 to fix the root issue.
---
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 zsxwing opened a pull request:
https://github.com/apache/spark/pull/17610
[SPARK-20131][Core]Use a separate lock for StandaloneSchedulerBackend.stop
## What changes were proposed in this pull request?
`o.a.s.streaming.StreamingContextSuite.SPARK-18560 Receiver
Github user sameeragarwal commented on a diff in the pull request:
https://github.com/apache/spark/pull/17265#discussion_r110985107
--- Diff:
sql/hive/src/main/scala/org/apache/spark/sql/hive/HiveExternalCatalog.scala ---
@@ -94,7 +96,13 @@ private[spark] class
Github user ioana-delaney commented on a diff in the pull request:
https://github.com/apache/spark/pull/17546#discussion_r110984951
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/optimizer/CostBasedJoinReorder.scala
---
@@ -54,8 +54,6 @@ case class
Github user BryanCutler commented on a diff in the pull request:
https://github.com/apache/spark/pull/16774#discussion_r110983267
--- Diff:
mllib/src/test/scala/org/apache/spark/ml/tuning/CrossValidatorSuite.scala ---
@@ -121,6 +121,33 @@ class CrossValidatorSuite
}
Github user mallman commented on the issue:
https://github.com/apache/spark/pull/15125
@felixcheung 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,
Github user hhbyyh commented on a diff in the pull request:
https://github.com/apache/spark/pull/17586#discussion_r110982571
--- Diff: python/pyspark/ml/classification.py ---
@@ -172,6 +172,47 @@ def intercept(self):
"""
return self._call_java("intercept")
Github user hhbyyh commented on a diff in the pull request:
https://github.com/apache/spark/pull/17586#discussion_r110982055
--- Diff:
mllib/src/main/scala/org/apache/spark/ml/classification/LinearSVC.scala ---
@@ -355,6 +368,19 @@ object LinearSVCModel extends
Github user hhbyyh commented on a diff in the pull request:
https://github.com/apache/spark/pull/17586#discussion_r110982433
--- Diff:
mllib/src/main/scala/org/apache/spark/ml/classification/LinearSVC.scala ---
@@ -287,6 +290,16 @@ class LinearSVCModel private[classification] (
Github user hhbyyh commented on a diff in the pull request:
https://github.com/apache/spark/pull/17586#discussion_r110981812
--- Diff:
mllib/src/main/scala/org/apache/spark/ml/classification/LinearSVC.scala ---
@@ -355,6 +368,19 @@ object LinearSVCModel extends
Github user hhbyyh commented on a diff in the pull request:
https://github.com/apache/spark/pull/17586#discussion_r110978675
--- Diff:
mllib/src/main/scala/org/apache/spark/ml/classification/LinearSVC.scala ---
@@ -287,6 +290,16 @@ class LinearSVCModel private[classification] (
Github user hhbyyh commented on a diff in the pull request:
https://github.com/apache/spark/pull/17586#discussion_r110980991
--- Diff:
examples/src/main/scala/org/apache/spark/examples/ml/LinearSVCExample.scala ---
@@ -44,6 +44,12 @@ object LinearSVCExample {
//
Github user hhbyyh commented on a diff in the pull request:
https://github.com/apache/spark/pull/17586#discussion_r110981511
--- Diff:
mllib/src/main/scala/org/apache/spark/ml/classification/LinearSVC.scala ---
@@ -355,6 +368,19 @@ object LinearSVCModel extends
Github user BryanCutler commented on a diff in the pull request:
https://github.com/apache/spark/pull/16774#discussion_r110981439
--- Diff:
mllib/src/main/scala/org/apache/spark/ml/tuning/CrossValidator.scala ---
@@ -100,31 +108,60 @@ class CrossValidator @Since("1.2.0")
Github user BryanCutler commented on a diff in the pull request:
https://github.com/apache/spark/pull/16774#discussion_r110980824
--- Diff:
mllib/src/main/scala/org/apache/spark/ml/tuning/ValidatorParams.scala ---
@@ -67,6 +71,39 @@ private[ml] trait ValidatorParams extends
Github user yanji84 commented on the issue:
https://github.com/apache/spark/pull/17109
@srowen is there anything else holding this up? why does it take so long?
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
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17606
**[Test build #75711 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/75711/testReport)**
for PR 17606 at commit
Github user dbtsai commented on the issue:
https://github.com/apache/spark/pull/17606
+cc @cloud-fan @gatorsmile @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 feature
enabled
Github user BryanCutler commented on a diff in the pull request:
https://github.com/apache/spark/pull/16774#discussion_r110979877
--- Diff:
mllib/src/main/scala/org/apache/spark/ml/tuning/ValidatorParams.scala ---
@@ -67,6 +71,39 @@ private[ml] trait ValidatorParams extends
Github user dbtsai commented on a diff in the pull request:
https://github.com/apache/spark/pull/17606#discussion_r110979361
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/analysis/TypeCoercion.scala
---
@@ -571,6 +571,7 @@ object TypeCoercion {
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17330
**[Test build #75710 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/75710/testReport)**
for PR 17330 at commit
Github user dilipbiswal commented on a diff in the pull request:
https://github.com/apache/spark/pull/17330#discussion_r110977254
--- Diff:
sql/core/src/test/scala/org/apache/spark/sql/CachedTableSuite.scala ---
@@ -670,4 +677,139 @@ class CachedTableSuite extends QueryTest with
Github user dilipbiswal commented on a diff in the pull request:
https://github.com/apache/spark/pull/17330#discussion_r110977330
--- Diff:
sql/core/src/test/scala/org/apache/spark/sql/CachedTableSuite.scala ---
@@ -670,4 +677,139 @@ class CachedTableSuite extends QueryTest with
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17609
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 jtoka opened a pull request:
https://github.com/apache/spark/pull/17609
[SPARK-20296][TRIVIAL][DOCS] Count distinct error message for streaming
## What changes were proposed in this pull request?
Update count distinct error message for streaming datasets/dataframes
Github user dilipbiswal commented on a diff in the pull request:
https://github.com/apache/spark/pull/17330#discussion_r110976069
--- Diff:
sql/core/src/test/scala/org/apache/spark/sql/CachedTableSuite.scala ---
@@ -76,6 +76,13 @@ class CachedTableSuite extends QueryTest with
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/17604
---
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 issue:
https://github.com/apache/spark/pull/17604
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 feature
enabled and wishes so, or
Github user mallman commented on the issue:
https://github.com/apache/spark/pull/17295
> LGTM, cc @mallman to check the unmap part
LGTM, too. Sorry for the late reply... I've been away the past two weeks.
---
If your project is set up for it, you can reply to this email and
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17436
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/75709/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17436
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/17436
**[Test build #75709 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/75709/testReport)**
for PR 17436 at commit
Github user AxenGitHub commented on the issue:
https://github.com/apache/spark/pull/7652
Is there any news on this branch? we would benefit a lot from this feature.
---
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 srowen commented on the issue:
https://github.com/apache/spark/pull/17527
The general idea is to leave any lower-casing that affects strings in the
user program alone, to use the locale-sensitive `toLowerCase()`. This is more
conservative. All of the changes should only
Github user ajbozarth commented on the issue:
https://github.com/apache/spark/pull/17455
It seems it didn't take @holdenk ok, @vanzin mind okaying this to 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 your
Github user ajbozarth commented on the issue:
https://github.com/apache/spark/pull/17608
@guoxiaolongzte This seems familiar, are you using the latest version of
Knox with your Spark UI?
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/17527
I am wondering what is the reason some of `toLowerCase` is changed, but the
others remain unchanged?
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user superbobry commented on a diff in the pull request:
https://github.com/apache/spark/pull/17598#discussion_r110950456
--- Diff: core/src/main/scala/org/apache/spark/serializer/Serializer.scala
---
@@ -125,7 +125,7 @@ abstract class SerializerInstance {
* A stream
Github user johnc1231 commented on the issue:
https://github.com/apache/spark/pull/17459
@viirya Do you have any more comments on this, or are you happy 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 AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/9571
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/75708/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/9571
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/9571
**[Test build #75708 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/75708/testReport)**
for PR 9571 at commit
Github user viirya commented on the issue:
https://github.com/apache/spark/pull/17491
I think the current approach will have a LeftSemi join for this Exists
subquery. Is it far from the optimal access plan you said?
---
If your project is set up for it, you can reply to this email
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17436
**[Test build #75709 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/75709/testReport)**
for PR 17436 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17150
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/75707/
Test PASSed.
---
Github user kiszk commented on a diff in the pull request:
https://github.com/apache/spark/pull/17436#discussion_r110923167
--- Diff: core/src/main/java/org/apache/spark/memory/MemoryConsumer.java ---
@@ -41,7 +41,7 @@ protected MemoryConsumer(TaskMemoryManager
taskMemoryManager,
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17150
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/17150
**[Test build #75707 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/75707/testReport)**
for PR 17150 at commit
Github user nsyca commented on the issue:
https://github.com/apache/spark/pull/17520
@cloud-fan: would you be interested in reviewing this PR since I have not
heard from @hvanhovell for a while? Note this is a WIP and I want to hear your
feedback on the issues I put in the comments
Github user nsyca commented on the issue:
https://github.com/apache/spark/pull/17491
@cloud-fan wrote: "How useful is this optimization? It only works when
Exists has no condition, is that a common case?"
One of the common cases of this usage is an application of ACL where
101 - 200 of 363 matches
Mail list logo
