Github user ala commented on the issue:
https://github.com/apache/spark/pull/16887
@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 and wishes so, or if the feature
GitHub user ala opened a pull request:
https://github.com/apache/spark/pull/16887
[SPARK-19549] Allow providing reason for stage/job cancelling
## What changes were proposed in this pull request?
This change add an optional argument to `SparkContext.cancelStage()` and
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16886
**[Test build #72711 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72711/testReport)**
for PR 16886 at commit
Github user maropu commented on a diff in the pull request:
https://github.com/apache/spark/pull/16886#discussion_r100549783
--- Diff:
sql/hive/src/main/scala/org/apache/spark/sql/hive/HiveInspectors.scala ---
@@ -218,22 +220,33 @@ private[hive] trait HiveInspectors {
Github user maropu commented on the issue:
https://github.com/apache/spark/pull/15928
@hvanhovell Could you have time to review 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
Github user maropu commented on a diff in the pull request:
https://github.com/apache/spark/pull/16886#discussion_r100547590
--- Diff:
sql/hive/src/main/scala/org/apache/spark/sql/hive/HiveInspectors.scala ---
@@ -218,22 +220,33 @@ private[hive] trait HiveInspectors {
Github user hvanhovell commented on a diff in the pull request:
https://github.com/apache/spark/pull/16886#discussion_r100545658
--- Diff:
sql/hive/src/main/scala/org/apache/spark/sql/hive/HiveInspectors.scala ---
@@ -218,22 +220,33 @@ private[hive] trait HiveInspectors {
Github user hvanhovell commented on a diff in the pull request:
https://github.com/apache/spark/pull/16886#discussion_r100544404
--- Diff:
sql/hive/src/main/scala/org/apache/spark/sql/hive/HiveInspectors.scala ---
@@ -218,22 +220,33 @@ private[hive] trait HiveInspectors {
Github user viirya commented on the issue:
https://github.com/apache/spark/pull/16865
Yeah, it makes sense. However, many other pieces in executor can better
respond to memory pressure. But this cache can't.
I don't say it definitely solves this issue because maybe other
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/13077
---
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/13077
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 srowen commented on the issue:
https://github.com/apache/spark/pull/16827
I just don't think that setting properties to override defaults, which is
the common reason this would occur, is a warning or error situation.
---
If your project is set up for it, you can reply to
Github user maropu commented on a diff in the pull request:
https://github.com/apache/spark/pull/16886#discussion_r100539896
--- Diff:
sql/hive/src/main/scala/org/apache/spark/sql/hive/HiveInspectors.scala ---
@@ -218,22 +220,33 @@ private[hive] trait HiveInspectors {
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13077
**[Test build #3573 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3573/testReport)**
for PR 13077 at commit
Github user maropu commented on a diff in the pull request:
https://github.com/apache/spark/pull/16886#discussion_r100540845
--- Diff:
sql/hive/src/main/scala/org/apache/spark/sql/hive/HiveInspectors.scala ---
@@ -218,22 +220,33 @@ private[hive] trait HiveInspectors {
Github user uncleGen commented on the issue:
https://github.com/apache/spark/pull/16827
@srowen make senses. What about logging a warning/error message if
'spark.master' is set with different values?
---
If your project is set up for it, you can reply to this email and have your
Github user hvanhovell commented on a diff in the pull request:
https://github.com/apache/spark/pull/16870#discussion_r100539828
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/datetimeExpressions.scala
---
@@ -465,15 +465,15 @@ case class
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16871
**[Test build #72709 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72709/testReport)**
for PR 16871 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16870
**[Test build #72710 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72710/testReport)**
for PR 16870 at commit
Github user maropu commented on the issue:
https://github.com/apache/spark/pull/16886
Looks great to me because Hive actually supports these types for `UDF`.
---
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 windpiger commented on a diff in the pull request:
https://github.com/apache/spark/pull/16870#discussion_r100539384
--- Diff:
sql/core/src/test/scala/org/apache/spark/sql/DateFunctionsSuite.scala ---
@@ -477,6 +475,24 @@ class DateFunctionsSuite extends QueryTest with
Github user windpiger commented on a diff in the pull request:
https://github.com/apache/spark/pull/16870#discussion_r100539442
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/util/DateTimeUtils.scala
---
@@ -95,9 +95,12 @@ object DateTimeUtils {
sdf
Github user hvanhovell commented on a diff in the pull request:
https://github.com/apache/spark/pull/16818#discussion_r100539109
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/window/BoundOrdering.scala
---
@@ -25,18 +25,22 @@ import
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/16827
I still don't see a reason to special-case this property. It also means you
can't override a property set by defaults, which could be a problem.
---
If your project is set up for it, you can reply
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13077
**[Test build #3573 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3573/testReport)**
for PR 13077 at commit
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/16884
---
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/16884
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 AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16886
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/72706/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16886
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 viirya commented on the issue:
https://github.com/apache/spark/pull/16785
@hvanhovell Yeah, I think so. As in previous comment, I don't find a way
now to improve `getAliasedConstraints` significantly by re-writing its logic
without parallel collection.
We may
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16886
**[Test build #72706 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72706/testReport)**
for PR 16886 at commit
Github user viirya commented on a diff in the pull request:
https://github.com/apache/spark/pull/16844#discussion_r100532958
--- Diff:
core/src/main/java/org/apache/spark/unsafe/map/BytesToBytesMap.java ---
@@ -695,11 +690,16 @@ public boolean append(Object kbase, long koff, int
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16882
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/16882
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/72701/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16882
**[Test build #72701 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72701/testReport)**
for PR 16882 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16857
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/72708/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16857
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/16857
**[Test build #72708 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72708/testReport)**
for PR 16857 at commit
Github user hvanhovell commented on the issue:
https://github.com/apache/spark/pull/16785
@viirya this looks like a very big hammer to solve this problem. Can't we
try a different approach?
I think we should try to avoid optimizing already optimized code snippets,
you might
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16883
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/72700/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16883
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/16883
**[Test build #72700 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72700/testReport)**
for PR 16883 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16857
**[Test build #72708 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72708/testReport)**
for PR 16857 at commit
Github user hvanhovell commented on a diff in the pull request:
https://github.com/apache/spark/pull/16870#discussion_r100523109
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/util/DateTimeUtils.scala
---
@@ -95,9 +95,12 @@ object DateTimeUtils {
sdf
Github user hvanhovell commented on a diff in the pull request:
https://github.com/apache/spark/pull/16870#discussion_r100523512
--- Diff:
sql/core/src/test/scala/org/apache/spark/sql/DateFunctionsSuite.scala ---
@@ -477,6 +475,24 @@ class DateFunctionsSuite extends QueryTest with
Github user hvanhovell commented on a diff in the pull request:
https://github.com/apache/spark/pull/16870#discussion_r100524361
--- Diff:
sql/core/src/test/scala/org/apache/spark/sql/DateFunctionsSuite.scala ---
@@ -500,6 +516,20 @@ class DateFunctionsSuite extends QueryTest with
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16883
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/72698/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16883
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/16883
**[Test build #72698 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72698/testReport)**
for PR 16883 at commit
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/16882
Oh, sure. Let me give a shot. Thank you for your quick review!
---
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 hvanhovell commented on the issue:
https://github.com/apache/spark/pull/16882
@HyukjinKwon Can you also improve the error message. I don't think
`StructType(StructField(_1,StringType,true), StructField(_2,StringType,true))
<> StructType(StructField(_1,StringType,true),
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16857
**[Test build #72705 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72705/testReport)**
for PR 16857 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16857
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/72705/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16857
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/14936
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/14936
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/72707/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14936
**[Test build #72707 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72707/testReport)**
for PR 14936 at commit
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/16881
---
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 commented on a diff in the pull request:
https://github.com/apache/spark/pull/16881#discussion_r100521142
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/jsonExpressions.scala
---
@@ -496,7 +496,7 @@ case class
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16883
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/72697/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16883
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/16883
**[Test build #72697 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72697/testReport)**
for PR 16883 at commit
Github user hvanhovell commented on the issue:
https://github.com/apache/spark/pull/16881
LGTM - merging to master/2.1. 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
Github user hvanhovell commented on a diff in the pull request:
https://github.com/apache/spark/pull/16881#discussion_r100520672
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/jsonExpressions.scala
---
@@ -496,7 +496,7 @@ case class
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16886
**[Test build #72706 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72706/testReport)**
for PR 16886 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14936
**[Test build #72707 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72707/testReport)**
for PR 14936 at commit
Github user viirya commented on a diff in the pull request:
https://github.com/apache/spark/pull/16844#discussion_r100518427
--- Diff:
core/src/main/java/org/apache/spark/unsafe/map/BytesToBytesMap.java ---
@@ -695,11 +690,16 @@ public boolean append(Object kbase, long koff, int
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16857
**[Test build #72705 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72705/testReport)**
for PR 16857 at commit
Github user vitillo commented on the issue:
https://github.com/apache/spark/pull/16857
@uncleGen I have added a new unit 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 project does not have this feature
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14936
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/72704/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14936
**[Test build #72704 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72704/testReport)**
for PR 14936 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14936
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/16886
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/16886
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/72703/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16886
**[Test build #72703 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72703/testReport)**
for PR 16886 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14936
**[Test build #72704 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72704/testReport)**
for PR 14936 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16886
**[Test build #72703 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72703/testReport)**
for PR 16886 at commit
Github user hvanhovell commented on the issue:
https://github.com/apache/spark/pull/16886
cc @cloud-fan @yhuai @maropu
---
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 hvanhovell opened a pull request:
https://github.com/apache/spark/pull/16886
[SPARK-19548][SQL] Support Hive UDFs which return typed Lists/Maps
## What changes were proposed in this pull request?
This PR adds support for Hive UDFs that return fully typed java Lists
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14936
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 SparkQA commented on the issue:
https://github.com/apache/spark/pull/14936
**[Test build #72702 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72702/testReport)**
for PR 14936 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14936
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/72702/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14936
**[Test build #72702 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72702/testReport)**
for PR 14936 at commit
Github user philipphoffmann commented on the issue:
https://github.com/apache/spark/pull/14936
rebase to master; added tests for all three schedulers
---
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 jinxing64 commented on the issue:
https://github.com/apache/spark/pull/16876
@kayousterhout
It's great to give a definition of `pendingPartitions` in `ShuffleMapStage`.
May I ask a question and make my understanding about `pendingPartitions`
clear ? It means:
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16882
**[Test build #72701 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72701/testReport)**
for PR 16882 at commit
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/16882
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 AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16885
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 dud225 opened a pull request:
https://github.com/apache/spark/pull/16885
Encryption of shuffle files
Hello
According to my understanding of commits
4b4e329e49f8af28fa6301bd06c48d7097eaf9e6 &
8b325b17ecdf013b7a6edcb7ee3773546bd914df, one may now encrypt shuffle
Github user bogdanrdc closed the pull request at:
https://github.com/apache/spark/pull/16875
---
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/16386
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/16386
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/72694/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16386
**[Test build #72694 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72694/testReport)**
for PR 16386 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16884
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/16884
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/72699/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16884
**[Test build #72699 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72699/testReport)**
for PR 16884 at commit
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/16864#discussion_r100503141
--- Diff:
common/sketch/src/main/java/org/apache/spark/util/sketch/BloomFilter.java ---
@@ -81,6 +81,11 @@ int getVersionNumber() {
public abstract
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16883
**[Test build #72700 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72700/testReport)**
for PR 16883 at commit
Github user rxin commented on the issue:
https://github.com/apache/spark/pull/16875
Merging in branch-2.1.
---
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 rxin commented on the issue:
https://github.com/apache/spark/pull/16875
@bogdanrdc can you close this? It won't auto close because it is not merged
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.
301 - 400 of 435 matches
Mail list logo
