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(
v
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 wishe
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 wishe
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 wishe
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 proj
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 fe
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 ena
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 ena
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,
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/14750
We still need to resolve the case sensitivity issues in
[`checkDuplication`](https://github.com/apache/spark/blob/6d86403d8b252776effcddd71338b4d21a224f9b/sql/core/src/main/scala/org/apache/spark/
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/14958
Merged to master/2.0/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 wishes
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/14958
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is ena
Github user vanzin commented on a diff in the pull request:
https://github.com/apache/spark/pull/14926#discussion_r77720376
--- Diff:
core/src/main/scala/org/apache/spark/ExecutorAllocationManager.scala ---
@@ -392,10 +397,36 @@ private[spark] class ExecutorAllocationManager(
Github user vanzin commented on the issue:
https://github.com/apache/spark/pull/14983
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 featu
Github user tgravescs commented on a diff in the pull request:
https://github.com/apache/spark/pull/14926#discussion_r77719621
--- Diff:
core/src/main/scala/org/apache/spark/ExecutorAllocationManager.scala ---
@@ -392,10 +397,36 @@ private[spark] class ExecutorAllocationManager(
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14983
**[Test build #65010 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/65010/consoleFull)**
for PR 14983 at commit
[`1ba43d6`](https://github.com/apache/spark/commit/1
Github user jkbradley commented on the issue:
https://github.com/apache/spark/pull/13036
Checking old PRs---is this active still? The ML parts look good to me. I
haven't checked the SQL ones carefully.
---
If your project is set up for it, you can reply to this email and have your
Github user zsxwing commented on the issue:
https://github.com/apache/spark/pull/14983
cc @vanzin
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the
GitHub user zsxwing opened a pull request:
https://github.com/apache/spark/pull/14983
[SPARK-17316][Core]Fix the 'ask' type parameter in 'removeExecutor'
## What changes were proposed in this pull request?
Fix the 'ask' type parameter in 'removeExecutor' to eliminate a lot o
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/14981
Leave the ganglia one because that artifact isn't an assembly after all.
Publishing the Spark part of that without redistributing the rest is OK.
Really, here we need to only pull the kinesi
Github user zsxwing commented on the issue:
https://github.com/apache/spark/pull/14961
I saw the error in the log:
```
16/09/05 08:21:56.758 shuffle-server-593-8 WARN TransportChannelHandler:
Exception in connection from /127.0.0.1:44788
io.netty.util.internal.OutOfDirectMe
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13762
**[Test build #3251 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3251/consoleFull)**
for PR 13762 at commit
[`22a3a04`](https://github.com/apache/spark/commit
Github user GayathriMurali commented on the issue:
https://github.com/apache/spark/pull/14112
@jkbradley I am so sorry I couldn't respond to this on time! I am in a
transition process and might not be able to drive this JIRA to completion at
this point in time. Thanks!
---
If your
Github user lresende commented on the issue:
https://github.com/apache/spark/pull/14981
As for the the Ganglia one, I will create another jira, to track that
separately as this (Kinesis) one might involve more changes around the python
and examples.
---
If your project is set up for
Github user jkbradley commented on the issue:
https://github.com/apache/spark/pull/13493
Pinging! Is this still active?
---
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 a
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13762
**[Test build #3251 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3251/consoleFull)**
for PR 13762 at commit
[`22a3a04`](https://github.com/apache/spark/commit/
Github user lresende commented on the issue:
https://github.com/apache/spark/pull/14981
@srowen, The Kinesis assembly has been published by Spark releases for a
while. Here is the link to the 2.0 release on repository.apache.org :
https://repository.apache.org/service/local/reposi
Github user jkbradley commented on the issue:
https://github.com/apache/spark/pull/14112
@GayathriMurali Btw, I know it's been a long time. If you no longer have
time to work on this, please say so, and I'd be happy to take it over. Thanks!
---
If your project is set up for it, you
Github user jkbradley commented on the issue:
https://github.com/apache/spark/pull/9440
Is this still active? If not, can you please close this issue pending
discussion on the JIRA? Thanks!
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user jkbradley commented on the issue:
https://github.com/apache/spark/pull/14834
+1 for Option 2: Store the binomial coefficients as a 1 x numFeatures
matrix.
It's such an important code path that I think it's worth avoiding the
regression for current users.
---
If
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14979
**[Test build #3250 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3250/consoleFull)**
for PR 14979 at commit
[`b3c5cfe`](https://github.com/apache/spark/commit/
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14978
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/65004/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14978
Merged build finished. Test PASSed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
e
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14978
**[Test build #65004 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/65004/consoleFull)**
for PR 14978 at commit
[`fab1730`](https://github.com/apache/spark/commit/
Github user atronchi commented on the issue:
https://github.com/apache/spark/pull/10970
This solution does not seem to work for datasets on tables using complex
types. e.g. Array[Int] still throws the exception `java.lang.AssertionError:
assertion failed: Unsound substitution from Lis
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14978
Merged build finished. Test PASSed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
e
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14978
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/65003/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14978
**[Test build #65003 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/65003/consoleFull)**
for PR 14978 at commit
[`a257bc5`](https://github.com/apache/spark/commit/
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/14981
Aha, right. That one is probably OK as there's technically no third-party
code distributed in those artifacts. However, this won't be OK:
https://mvnrepository.com/artifact/org.apache.spark/spark-str
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14979
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/65005/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14979
Merged build finished. Test FAILed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
e
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14979
**[Test build #65005 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/65005/consoleFull)**
for PR 14979 at commit
[`b3c5cfe`](https://github.com/apache/spark/commit/
Github user vanzin commented on the issue:
https://github.com/apache/spark/pull/14981
They're not in the assembly, but they're published to maven as a separate
thing; can that be an issue?
https://mvnrepository.com/artifact/org.apache.spark/spark-streaming-kinesis-asl_2.10
---
I
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/14981
@lresende I don't think we actually distribute the kinesis code, because
that profile just enables the kinesis assembly, and that does not cause this
stuff to get built into a Spark jar that's distri
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14980
Merged build finished. Test FAILed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
e
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14980
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/65007/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14980
**[Test build #65007 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/65007/consoleFull)**
for PR 14980 at commit
[`4386ab3`](https://github.com/apache/spark/commit/
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14982
**[Test build #65009 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/65009/consoleFull)**
for PR 14982 at commit
[`eab4b63`](https://github.com/apache/spark/commit/e
GitHub user sameeragarwal opened a pull request:
https://github.com/apache/spark/pull/14982
[WIP] Not re-use dictionary across batches
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/sameeragarwal/spark parquet-repro
Alternative
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14981
**[Test build #65008 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/65008/consoleFull)**
for PR 14981 at commit
[`375d62e`](https://github.com/apache/spark/commit/3
GitHub user lresende opened a pull request:
https://github.com/apache/spark/pull/14981
[SPARK-17418] Remove Kinesis artifacts from Spark release scripts
## What changes were proposed in this pull request?
This PR removes Kinesis from the release scripts as Kinesis license (Amazon
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14980
**[Test build #65007 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/65007/consoleFull)**
for PR 14980 at commit
[`4386ab3`](https://github.com/apache/spark/commit/4
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14980
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/65006/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14980
**[Test build #65006 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/65006/consoleFull)**
for PR 14980 at commit
[`cbd0b41`](https://github.com/apache/spark/commit/
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14980
Merged build finished. Test PASSed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
e
Github user junyangq commented on the issue:
https://github.com/apache/spark/pull/14980
cc @shivaram @felixcheung @mengxr
---
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/14980
**[Test build #65006 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/65006/consoleFull)**
for PR 14980 at commit
[`cbd0b41`](https://github.com/apache/spark/commit/c
Github user JoshRosen commented on a diff in the pull request:
https://github.com/apache/spark/pull/14952#discussion_r77699493
--- Diff: core/src/main/scala/org/apache/spark/storage/BlockManager.scala
---
@@ -520,10 +520,11 @@ private[spark] class BlockManager(
*
*
GitHub user junyangq opened a pull request:
https://github.com/apache/spark/pull/14980
[SPARK-17317][SparkR] Add SparkR vignette
## What changes were proposed in this pull request?
This PR tries to add a SparkR vignette, which works as a friendly guidance
going through the
Github user NarineK commented on the issue:
https://github.com/apache/spark/pull/14742
@liancheng, @rxin, Do you think adding `columns` to
`RelationalGroupedDataset` is reasonable or should we find a workaround on R
side ?
---
If your project is set up for it, you can reply to this
Github user markhamstra commented on a diff in the pull request:
https://github.com/apache/spark/pull/14952#discussion_r77697794
--- Diff: core/src/main/scala/org/apache/spark/storage/BlockManager.scala
---
@@ -520,10 +520,11 @@ private[spark] class BlockManager(
*
Github user BryanCutler commented on a diff in the pull request:
https://github.com/apache/spark/pull/14959#discussion_r77697522
--- Diff: python/pyspark/conf.py ---
@@ -101,13 +101,31 @@ def __init__(self, loadDefaults=True, _jvm=None,
_jconf=None):
self._jconf =
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14979
**[Test build #65005 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/65005/consoleFull)**
for PR 14979 at commit
[`b3c5cfe`](https://github.com/apache/spark/commit/b
Github user sameeragarwal commented on the issue:
https://github.com/apache/spark/pull/14979
cc @davies
---
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 gatorsmile commented on the issue:
https://github.com/apache/spark/pull/14978
cc @yhuai @cloud-fan @hvanhovell @wzhfy
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
Github user sameeragarwal commented on the issue:
https://github.com/apache/spark/pull/14979
Here is the list of changes with whitespaces ignored:
https://github.com/apache/spark/pull/14979/files?w=1
---
If your project is set up for it, you can reply to this email and have your
repl
Github user ericl commented on the issue:
https://github.com/apache/spark/pull/14952
looks 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 this feature
enabled and wishes so, or if the f
Github user gatorsmile commented on a diff in the pull request:
https://github.com/apache/spark/pull/14978#discussion_r77696450
--- Diff:
sql/hive/src/test/scala/org/apache/spark/sql/hive/StatisticsSuite.scala ---
@@ -171,23 +171,37 @@ class StatisticsSuite extends QueryTest with
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14978
**[Test build #65004 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/65004/consoleFull)**
for PR 14978 at commit
[`fab1730`](https://github.com/apache/spark/commit/f
GitHub user sameeragarwal opened a pull request:
https://github.com/apache/spark/pull/14979
Better error message for driver-side broadcast join OOMs
## What changes were proposed in this pull request?
This is a trivial patch that catches all `OutOfMemoryError` while building
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14978
**[Test build #65003 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/65003/consoleFull)**
for PR 14978 at commit
[`a257bc5`](https://github.com/apache/spark/commit/a
GitHub user gatorsmile opened a pull request:
https://github.com/apache/spark/pull/14978
[SPARK-17408] [TEST] Flaky test: org.apache.spark.sql.hive.StatisticsSuite
### What changes were proposed in this pull request?
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBui
Github user felixcheung commented on a diff in the pull request:
https://github.com/apache/spark/pull/14960#discussion_r77694632
--- Diff: core/src/main/scala/org/apache/spark/SparkContext.scala ---
@@ -992,7 +992,7 @@ class SparkContext(config: SparkConf) extends Logging
with Exec
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14809
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/65002/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14809
Merged build finished. Test PASSed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
e
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14809
**[Test build #65002 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/65002/consoleFull)**
for PR 14809 at commit
[`7caf2fb`](https://github.com/apache/spark/commit/
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14958
Merged build finished. Test PASSed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
e
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14958
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/65001/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14958
**[Test build #65001 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/65001/consoleFull)**
for PR 14958 at commit
[`022cad7`](https://github.com/apache/spark/commit/
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/14927
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is ena
Github user davies commented on the issue:
https://github.com/apache/spark/pull/14944
Merging this into 2.0 branch.
---
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 wi
Github user vanzin commented on a diff in the pull request:
https://github.com/apache/spark/pull/14926#discussion_r77684425
--- Diff:
core/src/main/scala/org/apache/spark/ExecutorAllocationManager.scala ---
@@ -392,10 +397,36 @@ private[spark] class ExecutorAllocationManager(
Github user dhruve commented on a diff in the pull request:
https://github.com/apache/spark/pull/14926#discussion_r77684087
--- Diff:
core/src/main/scala/org/apache/spark/ExecutorAllocationManager.scala ---
@@ -392,10 +397,36 @@ private[spark] class ExecutorAllocationManager(
Github user davies commented on the issue:
https://github.com/apache/spark/pull/14927
@hvanhovell Has lgtm offline. Other contributors also confirm that this
patch fix the bug, I'm going to merge this one into master and 2.0 branch.
---
If your project is set up for it, you can reply
Github user dhruve commented on a diff in the pull request:
https://github.com/apache/spark/pull/14926#discussion_r77683485
--- Diff:
core/src/main/scala/org/apache/spark/ExecutorAllocationManager.scala ---
@@ -392,10 +397,36 @@ private[spark] class ExecutorAllocationManager(
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/14712
These tests block multiple PRs. It is midnight in China. : ) Let me do a
quick fix based on the comments of @cloud-fan and @hvanhovell
---
If your project is set up for it, you can reply to thi
Github user dhruve commented on a diff in the pull request:
https://github.com/apache/spark/pull/14926#discussion_r77680444
--- Diff:
core/src/main/scala/org/apache/spark/ExecutorAllocationManager.scala ---
@@ -392,10 +397,36 @@ private[spark] class ExecutorAllocationManager(
Github user yhuai commented on the issue:
https://github.com/apache/spark/pull/14973
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 so, or if the feat
Github user yhuai commented on the issue:
https://github.com/apache/spark/pull/14968
@clockfly Can you close this? It has been merged to branch 2.0 (btw, prs
targeting branches other than master will not be auto-closed).
---
If your project is set up for it, you can reply to this em
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14809
**[Test build #65002 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/65002/consoleFull)**
for PR 14809 at commit
[`7caf2fb`](https://github.com/apache/spark/commit/7
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/14809
LGTM pending 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
enabled and wishes so,
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/14809
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 so
201 - 300 of 525 matches
Mail list logo
