Github user zsxwing commented on the issue:
https://github.com/apache/spark/pull/14987
LGTM pending tests
---
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 tdas commented on a diff in the pull request:
https://github.com/apache/spark/pull/14987#discussion_r77744980
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/streaming/HDFSMetadataLog.scala
---
@@ -49,6 +49,10 @@ import
Github user dbtsai commented on the issue:
https://github.com/apache/spark/pull/14834
@sethah Thank you for coming up with PR with detailed documentation. For
option 2, if a two class model is trained with multinomial family, how do you
store it? I was thinking about maybe we could
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14987
**[Test build #65015 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/65015/consoleFull)**
for PR 14987 at commit
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/14671
@davies Do you mind if I ask whether it is sensible to perform a benchmark
and try to submit a PR to disable this (maybe with adding an extra option to
enable/disable this but false by
Github user davies commented on the issue:
https://github.com/apache/spark/pull/14671
@andreweduffy Good point, but we still use the parquet-mr when there is any
complex type in the schema.
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user tdas commented on the issue:
https://github.com/apache/spark/pull/14987
@yhuai @zsxwing Can you take a look.
---
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 andreweduffy commented on the issue:
https://github.com/apache/spark/pull/14671
@davies Row-level filtering doesn't occur with the vectorized reader, which
is now enabled by default
---
If your project is set up for it, you can reply to this email and have your
reply
GitHub user tdas opened a pull request:
https://github.com/apache/spark/pull/14987
[SPARK-17372][SQL][STREAMING] Avoid serialization issues by using Arrays to
save file names in FileStreamSource
## What changes were proposed in this pull request?
When we create a
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/14919
Thanks @sameeragarwal !
---
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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/14978
---
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 cloud-fan commented on the issue:
https://github.com/apache/spark/pull/14978
thanks, merging 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
Github user felixcheung commented on a diff in the pull request:
https://github.com/apache/spark/pull/14980#discussion_r77740936
--- Diff: R/pkg/vignettes/sparkr-vignettes.Rmd ---
@@ -0,0 +1,853 @@
+---
+title: "SparkR - Practical Guide"
+output:
+ html_document:
Github user felixcheung commented on a diff in the pull request:
https://github.com/apache/spark/pull/14980#discussion_r77740858
--- Diff: R/pkg/vignettes/sparkr-vignettes.Rmd ---
@@ -0,0 +1,853 @@
+---
+title: "SparkR - Practical Guide"
+output:
+ html_document:
Github user clockfly closed the pull request at:
https://github.com/apache/spark/pull/14973
---
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 cloud-fan commented on the issue:
https://github.com/apache/spark/pull/10970
@atronchi can you create a JIRA and put the code that can reproduce the
bug? thanks!
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user felixcheung commented on a diff in the pull request:
https://github.com/apache/spark/pull/14980#discussion_r77740557
--- Diff: R/pkg/vignettes/sparkr-vignettes.Rmd ---
@@ -0,0 +1,853 @@
+---
+title: "SparkR - Practical Guide"
+output:
+ html_document:
Github user felixcheung commented on a diff in the pull request:
https://github.com/apache/spark/pull/14980#discussion_r77740392
--- Diff: R/pkg/vignettes/sparkr-vignettes.Rmd ---
@@ -0,0 +1,853 @@
+---
+title: "SparkR - Practical Guide"
+output:
+ html_document:
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/14932
---
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 felixcheung commented on a diff in the pull request:
https://github.com/apache/spark/pull/14980#discussion_r77740084
--- Diff: R/pkg/vignettes/sparkr-vignettes.Rmd ---
@@ -0,0 +1,853 @@
+---
+title: "SparkR - Practical Guide"
+output:
+ html_document:
Github user JoshRosen commented on the issue:
https://github.com/apache/spark/pull/14932
@ericl and I discussed this and decided to address the file cleanup issues
that I mentioned above in a separate PR: the issues that I outlined above can
generally only occur in cases where we've
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/14983
---
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 zsxwing commented on the issue:
https://github.com/apache/spark/pull/14983
Merging to master, 2.0 and 1.6
---
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 davies commented on the issue:
https://github.com/apache/spark/pull/14671
Before disable the record level filter in parquet reader, I think pushing
more non-efficient predicates into parquet reader will be even worse, right?
---
If your project is set up for it, you can
Github user vanzin commented on the issue:
https://github.com/apache/spark/pull/14931
This looks ok from what I read of the standalone code, but probably someone
more familiar with standalone should take a look. @JoshRosen ?
---
If your project is set up for it, you can reply to
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14983
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/65010/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14983
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/14983
**[Test build #65010 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/65010/consoleFull)**
for PR 14983 at commit
Github user andreweduffy commented on the issue:
https://github.com/apache/spark/pull/14671
cool, ping to @davies @cloud-fan would either of you be able to look at
this?
---
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 thunterdb commented on the issue:
https://github.com/apache/spark/pull/14976
By the way, you gave some great advice here. Is there a page on the wiki
where we collect all this internal knowledge?
---
If your project is set up for it, you can reply to this email and have
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14986
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 sethah commented on a diff in the pull request:
https://github.com/apache/spark/pull/9#discussion_r77737542
--- Diff: mllib/src/main/scala/org/apache/spark/ml/util/ReadWrite.scala ---
@@ -446,6 +463,20 @@ private[ml] object DefaultParamsReader {
val cls =
Github user sethah commented on a diff in the pull request:
https://github.com/apache/spark/pull/9#discussion_r77737428
--- Diff: mllib/src/main/scala/org/apache/spark/ml/util/ReadWrite.scala ---
@@ -446,6 +463,20 @@ private[ml] object DefaultParamsReader {
val cls =
Github user sethah commented on a diff in the pull request:
https://github.com/apache/spark/pull/9#discussion_r77737335
--- Diff:
mllib/src/test/scala/org/apache/spark/ml/clustering/KMeansSuite.scala ---
@@ -139,16 +146,61 @@ class KMeansSuite extends SparkFunSuite with
GitHub user frreiss opened a pull request:
https://github.com/apache/spark/pull/14986
[WIP] [SPARK-17421] Don't use -XX:MaxPermSize option when Java version >= 8
## What changes were proposed in this pull request?
Modifies the `build/mvn` and `build/sbt-launch-lib.bash`
Github user sethah commented on a diff in the pull request:
https://github.com/apache/spark/pull/9#discussion_r77737026
--- Diff: mllib/src/main/scala/org/apache/spark/ml/clustering/KMeans.scala
---
@@ -303,6 +322,29 @@ class KMeans @Since("1.5.0") (
@Since("1.5.0")
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14816
**[Test build #65014 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/65014/consoleFull)**
for PR 14816 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14985
**[Test build #65012 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/65012/consoleFull)**
for PR 14985 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14984
**[Test build #65013 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/65013/consoleFull)**
for PR 14984 at commit
GitHub user rdblue opened a pull request:
https://github.com/apache/spark/pull/14985
[SPARK-17396][core] Share the task support between UnionRDD instances.
## What changes were proposed in this pull request?
Share the ForkJoinTaskSupport between UnionRDD instances to avoid
GitHub user hvanhovell opened a pull request:
https://github.com/apache/spark/pull/14984
[SPARK-17296
## What changes were proposed in this pull request?
This PR backports https://github.com/apache/spark/pull/14867 to branch-2.0.
It fixes a number of join ordering bugs.
##
Github user JoshRosen commented on the issue:
https://github.com/apache/spark/pull/14932
Context for other reviewers:
As of #9610 (Spark 1.5.3+), map tasks write their output to temporary files
and then atomically rename those files to put them at the final destination
path.
Github user yhuai commented on the issue:
https://github.com/apache/spark/pull/14816
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 wishes so, or
Github user thunterdb commented on the issue:
https://github.com/apache/spark/pull/14976
@srowen LGTM, 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
enabled and wishes
Github user thunterdb commented on a diff in the pull request:
https://github.com/apache/spark/pull/14976#discussion_r77735611
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/util/QuantileSummaries.scala
---
@@ -236,7 +240,7 @@ object QuantileSummaries {
Github user sethah commented on a diff in the pull request:
https://github.com/apache/spark/pull/9#discussion_r77734912
--- Diff: mllib/src/main/scala/org/apache/spark/ml/util/ReadWrite.scala ---
@@ -318,6 +327,14 @@ private[ml] object DefaultParamsWriter {
val
Github user sethah commented on a diff in the pull request:
https://github.com/apache/spark/pull/9#discussion_r77734849
--- Diff: mllib/src/main/scala/org/apache/spark/ml/util/ReadWrite.scala ---
@@ -318,6 +327,14 @@ private[ml] object DefaultParamsWriter {
val
Github user felixcheung commented on a diff in the pull request:
https://github.com/apache/spark/pull/14980#discussion_r77734883
--- Diff: R/pkg/vignettes/sparkr-vignettes.Rmd ---
@@ -0,0 +1,853 @@
+---
+title: "SparkR - Practical Guide"
+output:
+ html_document:
Github user felixcheung commented on a diff in the pull request:
https://github.com/apache/spark/pull/14980#discussion_r77734719
--- Diff: R/pkg/vignettes/sparkr-vignettes.Rmd ---
@@ -0,0 +1,853 @@
+---
+title: "SparkR - Practical Guide"
+output:
+ html_document:
Github user felixcheung commented on a diff in the pull request:
https://github.com/apache/spark/pull/14980#discussion_r77734604
--- Diff: R/pkg/vignettes/sparkr-vignettes.Rmd ---
@@ -0,0 +1,853 @@
+---
+title: "SparkR - Practical Guide"
+output:
+ html_document:
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14702
**[Test build #65011 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/65011/consoleFull)**
for PR 14702 at commit
Github user felixcheung commented on a diff in the pull request:
https://github.com/apache/spark/pull/14980#discussion_r77734509
--- Diff: R/pkg/vignettes/sparkr-vignettes.Rmd ---
@@ -0,0 +1,853 @@
+---
+title: "SparkR - Practical Guide"
+output:
+ html_document:
Github user thunterdb commented on a diff in the pull request:
https://github.com/apache/spark/pull/14976#discussion_r77734419
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/util/QuantileSummaries.scala
---
@@ -59,9 +59,14 @@ class QuantileSummaries(
Github user felixcheung commented on a diff in the pull request:
https://github.com/apache/spark/pull/14980#discussion_r77733682
--- Diff: R/pkg/vignettes/sparkr-vignettes.Rmd ---
@@ -0,0 +1,853 @@
+---
+title: "SparkR - Practical Guide"
+output:
+ html_document:
Github user felixcheung commented on a diff in the pull request:
https://github.com/apache/spark/pull/14980#discussion_r77734337
--- Diff: R/pkg/vignettes/sparkr-vignettes.Rmd ---
@@ -0,0 +1,853 @@
+---
+title: "SparkR - Practical Guide"
+output:
+ html_document:
Github user felixcheung commented on a diff in the pull request:
https://github.com/apache/spark/pull/14980#discussion_r77734227
--- Diff: R/pkg/vignettes/sparkr-vignettes.Rmd ---
@@ -0,0 +1,853 @@
+---
+title: "SparkR - Practical Guide"
+output:
+ html_document:
Github user felixcheung commented on a diff in the pull request:
https://github.com/apache/spark/pull/14980#discussion_r77734065
--- Diff: R/pkg/vignettes/sparkr-vignettes.Rmd ---
@@ -0,0 +1,853 @@
+---
+title: "SparkR - Practical Guide"
+output:
+ html_document:
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/14943
---
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 felixcheung commented on a diff in the pull request:
https://github.com/apache/spark/pull/14980#discussion_r77733949
--- Diff: R/pkg/vignettes/sparkr-vignettes.Rmd ---
@@ -0,0 +1,853 @@
+---
+title: "SparkR - Practical Guide"
+output:
+ html_document:
Github user felixcheung commented on a diff in the pull request:
https://github.com/apache/spark/pull/14980#discussion_r77733925
--- Diff: R/pkg/vignettes/sparkr-vignettes.Rmd ---
@@ -0,0 +1,853 @@
+---
+title: "SparkR - Practical Guide"
+output:
+ html_document:
Github user felixcheung commented on a diff in the pull request:
https://github.com/apache/spark/pull/14980#discussion_r77733824
--- Diff: R/pkg/vignettes/sparkr-vignettes.Rmd ---
@@ -0,0 +1,853 @@
+---
+title: "SparkR - Practical Guide"
+output:
+ html_document:
Github user vanzin commented on the issue:
https://github.com/apache/spark/pull/14943
Merging 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,
Github user felixcheung commented on a diff in the pull request:
https://github.com/apache/spark/pull/14980#discussion_r77733377
--- Diff: R/pkg/vignettes/sparkr-vignettes.Rmd ---
@@ -0,0 +1,853 @@
+---
+title: "SparkR - Practical Guide"
+output:
+ html_document:
Github user felixcheung commented on a diff in the pull request:
https://github.com/apache/spark/pull/14980#discussion_r77733194
--- Diff: R/pkg/vignettes/sparkr-vignettes.Rmd ---
@@ -0,0 +1,853 @@
+---
+title: "SparkR - Practical Guide"
+output:
+ html_document:
Github user felixcheung commented on a diff in the pull request:
https://github.com/apache/spark/pull/14980#discussion_r77733088
--- Diff: R/pkg/vignettes/sparkr-vignettes.Rmd ---
@@ -0,0 +1,853 @@
+---
+title: "SparkR - Practical Guide"
+output:
+ html_document:
Github user felixcheung commented on a diff in the pull request:
https://github.com/apache/spark/pull/14980#discussion_r77732888
--- Diff: R/pkg/vignettes/sparkr-vignettes.Rmd ---
@@ -0,0 +1,853 @@
+---
+title: "SparkR - Practical Guide"
+output:
+ html_document:
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/14867
---
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 hvanhovell commented on the issue:
https://github.com/apache/spark/pull/14867
Merging to master/2.0. Thanks for the 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 does not have this
Github user zsxwing commented on the issue:
https://github.com/apache/spark/pull/14961
I think we can binary search the first broken netty version. It would be
easy to find out the real issue.
---
If your project is set up for it, you can reply to this email and have your
reply
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14979
**[Test build #3250 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3250/consoleFull)**
for PR 14979 at commit
Github user yinxusen commented on the issue:
https://github.com/apache/spark/pull/9
@dbtsai It's ready for your 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 does not have this feature
Github user sameeragarwal closed the pull request at:
https://github.com/apache/spark/pull/14982
---
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
Github user lresende commented on the issue:
https://github.com/apache/spark/pull/14981
Spark kinesis has dependency on the kinesis client which is category-x
com.amazonaws
amazon-kinesis-client
${aws.kinesis.client.version}
Thus
Github user sameeragarwal closed the pull request at:
https://github.com/apache/spark/pull/14944
---
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
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14981
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/14981
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/65008/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14981
**[Test build #65008 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/65008/consoleFull)**
for PR 14981 at commit
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/14952
---
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 JoshRosen commented on the issue:
https://github.com/apache/spark/pull/14952
I'm going to merge this into master and branch-2.0 as an immediate fix for
the PySpark caching issue.
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14982
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/14982
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/65009/
Test PASSed.
---
Github user clockfly commented on a diff in the pull request:
https://github.com/apache/spark/pull/14976#discussion_r77727133
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/util/QuantileSummaries.scala
---
@@ -59,9 +59,14 @@ class QuantileSummaries(
*
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14982
**[Test build #65009 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/65009/consoleFull)**
for PR 14982 at commit
Github user clockfly commented on a diff in the pull request:
https://github.com/apache/spark/pull/14976#discussion_r77726882
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/util/QuantileSummaries.scala
---
@@ -59,9 +59,14 @@ class QuantileSummaries(
*
Github user dhruve commented on a diff in the pull request:
https://github.com/apache/spark/pull/14926#discussion_r77724521
--- Diff:
core/src/main/scala/org/apache/spark/ExecutorAllocationManager.scala ---
@@ -392,10 +397,36 @@ private[spark] class ExecutorAllocationManager(
Github user tgravescs commented on a diff in the pull request:
https://github.com/apache/spark/pull/14926#discussion_r77723977
--- Diff:
core/src/main/scala/org/apache/spark/ExecutorAllocationManager.scala ---
@@ -392,10 +397,36 @@ private[spark] class ExecutorAllocationManager(
Github user zsxwing commented on the issue:
https://github.com/apache/spark/pull/14961
> Is the lesson here to not bother with pooling and use the
UnpooledByteBufAllocator?
Not sure. Pooling is for improving the performance because allocating
direct buffers is pretty slow.
Github user vanzin commented on a diff in the pull request:
https://github.com/apache/spark/pull/14943#discussion_r77722666
--- Diff:
yarn/src/main/scala/org/apache/spark/deploy/yarn/ExecutorRunnable.scala ---
@@ -59,43 +58,46 @@ private[yarn] class ExecutorRunnable(
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/14961
Aha, possibly this:
https://groups.google.com/forum/#!topic/netty/3BoF7q34Z4I
Is the lesson here to not bother with pooling and use the
UnpooledByteBufAllocator?
---
If your project is
Github user tgravescs commented on the issue:
https://github.com/apache/spark/pull/14943
+1 feel free to commit.
---
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 tgravescs commented on the issue:
https://github.com/apache/spark/pull/14943
+1 feel free to commit.
---
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 tgravescs commented on the issue:
https://github.com/apache/spark/pull/14943
+1 feel free to commit.
---
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 tgravescs commented on a diff in the pull request:
https://github.com/apache/spark/pull/14943#discussion_r77722010
--- Diff:
yarn/src/main/scala/org/apache/spark/deploy/yarn/ExecutorRunnable.scala ---
@@ -59,43 +58,46 @@ private[yarn] class ExecutorRunnable(
Github user sethah commented on the issue:
https://github.com/apache/spark/pull/14834
@jkbradley Thanks for your input. Let's see what @dbtsai thinks as well :)
---
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 hvanhovell commented on the issue:
https://github.com/apache/spark/pull/14927
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
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/14972
---
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/14924
---
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 jkbradley commented on the issue:
https://github.com/apache/spark/pull/14972
I'm OK with this not having a JIRA, and I agree the code path is tested
sufficiently. (But wanting these is a good sentiment!)
LGTM
Merging with master
---
If your project is set up for
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/14924
Merged to master/2.0
---
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 srowen commented on the issue:
https://github.com/apache/spark/pull/14924
Merged to master/2.0
---
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,
101 - 200 of 525 matches
Mail list logo
