Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16135
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/16220
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69981/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16248
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 felixcheung reopened a pull request:
https://github.com/apache/spark/pull/16248
[SPARK-18810][SPARKR] SparkR install.spark does not work for RCs, snapshots
## What changes were proposed in this pull request?
Support overriding the download url (include version
Github user felixcheung closed the pull request at:
https://github.com/apache/spark/pull/16248
---
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 SparkQA commented on the issue:
https://github.com/apache/spark/pull/16248
**[Test build #69984 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69984/consoleFull)**
for PR 16248 at commit
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/16244
---
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 a-roberts commented on the issue:
https://github.com/apache/spark/pull/16196
Agreed, I'll be back working on this and answering the queries after the
2.1.0 release vote passes, that's my current priority as we're nearing the
Christmas break period
---
If your project is
Github user Mironor commented on a diff in the pull request:
https://github.com/apache/spark/pull/16137#discussion_r91856040
--- Diff: core/src/main/scala/org/apache/spark/SparkContext.scala ---
@@ -956,24 +976,24 @@ class SparkContext(config: SparkConf) extends Logging
{
}
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16220
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/16248
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69982/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16135
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69979/
Test FAILed.
---
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/16236
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/13944
@meknio if you'll update as Marcelo says, I'll merge this. Change the
description here to contain your comment at
https://github.com/apache/spark/pull/13944#issuecomment-229395810
---
If your
Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/16179#discussion_r91852909
--- Diff:
sql/hive/src/test/scala/org/apache/spark/sql/hive/execution/HiveCommandSuite.scala
---
@@ -168,14 +200,50 @@ class HiveCommandSuite extends
Github user Mironor commented on the issue:
https://github.com/apache/spark/pull/16137
@srowen I see that my rebase didn't go well, sorry for that. Is there a way
to revert the last push or it would be better to create another pull request
and close this one?
---
If your project is
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/16242
---
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/16086
Unless someone vigorously objects, yes let's close 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
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/15915
@uncleGen can you follow up on this so we can finish this out?
---
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 cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/16179#discussion_r91853357
--- Diff:
sql/hive/src/test/scala/org/apache/spark/sql/hive/execution/HiveCommandSuite.scala
---
@@ -190,87 +258,39 @@ class HiveCommandSuite extends
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/16137
Up to you but it's fine to just start from scratch in a new PR. Sometimes
that's simpler, esp. because it will probably be fairly different anyway.
---
If your project is set up for it, you can
Github user viirya commented on the issue:
https://github.com/apache/spark/pull/16245
I will create Jira and add test for this later.
---
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 cloud-fan commented on the issue:
https://github.com/apache/spark/pull/16179
LGTM except 2 minor comments:
https://github.com/apache/spark/pull/16179#discussion_r91852909 and
https://github.com/apache/spark/pull/16179#discussion_r91846277
---
If your project is set up
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16249
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69983/
Test FAILed.
---
Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/16104#discussion_r91853527
--- Diff:
sql/hive/src/main/scala/org/apache/spark/sql/hive/execution/InsertIntoHiveTable.scala
---
@@ -86,14 +85,15 @@ case class InsertIntoHiveTable(
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16249
**[Test build #69983 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69983/consoleFull)**
for PR 16249 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16249
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 cloud-fan commented on the issue:
https://github.com/apache/spark/pull/16104
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 Mironor commented on the issue:
https://github.com/apache/spark/pull/16137
@srowen I fixed everything. All comments are squashed, please review the
current one.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15995
**[Test build #69986 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69986/consoleFull)**
for PR 15995 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16104
**[Test build #69985 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69985/consoleFull)**
for PR 16104 at commit
Github user WeichenXu123 commented on the issue:
https://github.com/apache/spark/pull/15730
@brkyvz All right, I'll update code ASAP. 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
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16248
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/16248
**[Test build #69984 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69984/consoleFull)**
for PR 16248 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16248
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69984/
Test PASSed.
---
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/15713
Although I'd love to find we can get rid of a custom collections class, it
seems like we can't do that and that the optimization here doesn't result in a
win. Let's close this for now.
---
If your
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16104
**[Test build #69985 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69985/consoleFull)**
for PR 16104 at commit
Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/16134#discussion_r91853572
--- Diff:
sql/hive/src/test/scala/org/apache/spark/sql/hive/InsertIntoHiveTableSuite.scala
---
@@ -166,6 +166,30 @@ class InsertIntoHiveTableSuite
Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/13909#discussion_r91853950
--- Diff:
sql/catalyst/src/main/java/org/apache/spark/sql/catalyst/expressions/codegen/BufferHolder.java
---
@@ -55,6 +58,15 @@ public
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/16137#discussion_r91855221
--- Diff: core/src/main/scala/org/apache/spark/SparkContext.scala ---
@@ -816,6 +833,10 @@ class SparkContext(config: SparkConf) extends Logging {
/**
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/16137#discussion_r91855239
--- Diff: core/src/main/scala/org/apache/spark/SparkContext.scala ---
@@ -816,6 +833,10 @@ class SparkContext(config: SparkConf) extends Logging {
/**
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/16137#discussion_r91855254
--- Diff: core/src/main/scala/org/apache/spark/SparkContext.scala ---
@@ -956,24 +976,24 @@ class SparkContext(config: SparkConf) extends Logging
{
}
Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/15995#discussion_r91855259
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/datasources/DataSourceStrategy.scala
---
@@ -192,19 +200,13 @@ case class
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/16137#discussion_r91855172
--- Diff: core/src/main/scala/org/apache/spark/SparkContext.scala ---
@@ -486,9 +491,11 @@ class SparkContext(config: SparkConf) extends Logging {
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/16137#discussion_r91855194
--- Diff: core/src/main/scala/org/apache/spark/SparkContext.scala ---
@@ -721,16 +732,15 @@ class SparkContext(config: SparkConf) extends Logging
{
}
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/16137#discussion_r91855158
--- Diff: core/src/main/scala/org/apache/spark/SparkContext.scala ---
@@ -276,6 +276,9 @@ class SparkContext(config: SparkConf) extends Logging {
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/16137#discussion_r91855251
--- Diff: core/src/main/scala/org/apache/spark/SparkContext.scala ---
@@ -956,24 +976,24 @@ class SparkContext(config: SparkConf) extends Logging
{
}
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/16137#discussion_r91855189
--- Diff: core/src/main/scala/org/apache/spark/SparkContext.scala ---
@@ -705,13 +712,17 @@ class SparkContext(config: SparkConf) extends Logging
{
GitHub user felixcheung opened a pull request:
https://github.com/apache/spark/pull/16249
[SPARKR] Refactor scripts for R
## What changes were proposed in this pull request?
Refactored script to remove duplications and clearer purpose for each script
## How was
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16249
**[Test build #69983 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69983/consoleFull)**
for PR 16249 at commit
Github user viirya commented on the issue:
https://github.com/apache/spark/pull/16244
@cloud-fan Ok. I see. 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
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/16145#discussion_r91851737
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/ShuffledRowRDD.scala ---
@@ -117,7 +113,7 @@ class CoalescedPartitioner(val parent:
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/15736
@a-roberts let's either finish the thought and merge this as mostly a code
cleanup and maybe marginal win, or just close it.
---
If your project is set up for it, you can reply to this email and
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/16137
Ping @Mironor are you able to pare this down further? I want to figure out
whether this will proceed or not. It needs a rebase anyhow.
---
If your project is set up for it, you can reply to this
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/14638
I am really on the fence about it. I can see the argument that it's useful
to support, and not hard to support. But also that this is just one of many
Hive features that one could support, and we
Github user cloud-fan commented on the issue:
https://github.com/apache/spark/pull/15717
Why can't we remove `alterTableComment`? It seems that the implementations
are same, so we can make it a util function to map alter column comment action
to `alterTable` call.
---
If your
Github user kiszk commented on a diff in the pull request:
https://github.com/apache/spark/pull/13909#discussion_r91854780
--- Diff:
sql/catalyst/src/main/java/org/apache/spark/sql/catalyst/expressions/codegen/BufferHolder.java
---
@@ -55,6 +58,15 @@ public BufferHolder(UnsafeRow
Github user kiszk commented on a diff in the pull request:
https://github.com/apache/spark/pull/13909#discussion_r91854826
--- Diff:
sql/catalyst/src/main/java/org/apache/spark/sql/catalyst/expressions/codegen/BufferHolder.java
---
@@ -55,6 +58,15 @@ public BufferHolder(UnsafeRow
Github user lins05 commented on a diff in the pull request:
https://github.com/apache/spark/pull/16189#discussion_r91855053
--- Diff: core/src/main/scala/org/apache/spark/executor/Executor.scala ---
@@ -432,6 +458,78 @@ private[spark] class Executor(
}
/**
+
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16104
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69985/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16104
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 cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/13909#discussion_r91855403
--- Diff:
sql/catalyst/src/main/java/org/apache/spark/sql/catalyst/expressions/codegen/BufferHolder.java
---
@@ -55,6 +58,15 @@ public
Github user felixcheung commented on the issue:
https://github.com/apache/spark/pull/16248
Jenkins, 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
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/16244
Merged to master and 2.1, in order to see if this resolves the test
failures for 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.
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/16236
---
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/16196
Ping @a-roberts -- I think some sections of this are clearly a win, like
near https://github.com/apache/spark/pull/16196#discussion_r91270660 but maybe
best to back out anything controversial. And
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/16194
Yes, it would be nicer to just have a default like `ClassName(uid=...)` at
least. That however would not include the class-specific details like number of
layers. I am neutral on whether that's so
Github user lins05 commented on a diff in the pull request:
https://github.com/apache/spark/pull/16189#discussion_r91855204
--- Diff: core/src/main/scala/org/apache/spark/executor/Executor.scala ---
@@ -432,6 +458,78 @@ private[spark] class Executor(
}
/**
+
Github user lins05 commented on a diff in the pull request:
https://github.com/apache/spark/pull/16189#discussion_r91856289
--- Diff: core/src/main/scala/org/apache/spark/executor/Executor.scala ---
@@ -432,6 +458,78 @@ private[spark] class Executor(
}
/**
+
Github user winningsix commented on the issue:
https://github.com/apache/spark/pull/11045
@yaooqinn yes, the validation is working on server side.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
Github user kiszk commented on the issue:
https://github.com/apache/spark/pull/16086
I am thinking about an simpler approach. However, it is fine to close for
now.
---
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 rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/16245#discussion_r91881557
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/optimizer/expressions.scala
---
@@ -514,6 +514,25 @@ case class OptimizeCodegen(conf:
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16135
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69998/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16135
**[Test build #69998 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69998/consoleFull)**
for PR 16135 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16135
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 a diff in the pull request:
https://github.com/apache/spark/pull/16245#discussion_r91886133
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/optimizer/expressions.scala
---
@@ -514,6 +514,25 @@ case class OptimizeCodegen(conf:
GitHub user wangyum opened a pull request:
https://github.com/apache/spark/pull/16252
[SPARK-18827][Core] Fix cannot read broadcast on disk
## What changes were proposed in this pull request?
Fix cannot read broadcast on disk
## How was this patch tested?
Add
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15915
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/70001/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15915
**[Test build #70001 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70001/consoleFull)**
for PR 15915 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15915
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/16104
**[Test build #70006 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70006/consoleFull)**
for PR 16104 at commit
Github user dongjoon-hyun commented on the issue:
https://github.com/apache/spark/pull/14638
Do you mean to replace the current whole `TableReader.scala` which was
introduced in SPARK-1251 ? I guessed Spark chose this direct access approach
for the performance issue at that time.
Github user uncleGen commented on a diff in the pull request:
https://github.com/apache/spark/pull/15915#discussion_r9169
--- Diff:
core/src/main/scala/org/apache/spark/broadcast/TorrentBroadcast.scala ---
@@ -78,6 +80,7 @@ private[spark] class TorrentBroadcast[T:
Github user uncleGen commented on a diff in the pull request:
https://github.com/apache/spark/pull/16142#discussion_r91889826
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/EventLoggingListener.scala ---
@@ -90,6 +91,10 @@ private[spark] class EventLoggingListener(
Github user cloud-fan commented on the issue:
https://github.com/apache/spark/pull/16030
the new behavior LGTM, but I'm not sure if we still need to keep the old
behavior
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well.
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16220
**[Test build #70003 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70003/consoleFull)**
for PR 16220 at commit
Github user xuanyuanking commented on a diff in the pull request:
https://github.com/apache/spark/pull/16135#discussion_r91879183
--- Diff:
core/src/main/scala/org/apache/spark/metrics/source/StaticSources.scala ---
@@ -105,6 +111,7 @@ object HiveCatalogMetrics extends Source {
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16214
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/16220
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/16219
**[Test build #3493 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3493/consoleFull)**
for PR 16219 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16220
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/70003/
Test PASSed.
---
Github user viirya commented on a diff in the pull request:
https://github.com/apache/spark/pull/13909#discussion_r91881279
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/complexTypeCreator.scala
---
@@ -56,33 +58,93 @@ case class
Github user shivaram commented on the issue:
https://github.com/apache/spark/pull/16249
Can we open a JIRA for this ? Its good to track this change
---
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 zsxwing commented on the issue:
https://github.com/apache/spark/pull/16220
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,
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/16104
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 viirya commented on a diff in the pull request:
https://github.com/apache/spark/pull/15915#discussion_r91893984
--- Diff:
core/src/main/scala/org/apache/spark/storage/memory/MemoryStore.scala ---
@@ -331,7 +332,7 @@ private[spark] class MemoryStore(
var
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16251
**[Test build #70002 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70002/consoleFull)**
for PR 16251 at commit
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/16219
---
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 YuhuWang2002 commented on the issue:
https://github.com/apache/spark/pull/15297
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 uncleGen commented on a diff in the pull request:
https://github.com/apache/spark/pull/15915#discussion_r91880781
--- Diff: core/src/main/scala/org/apache/spark/memory/MemoryManager.scala
---
@@ -223,8 +222,10 @@ private[spark] abstract class MemoryManager(
1 - 100 of 233 matches
Mail list logo
