Github user mateiz commented on a diff in the pull request:
https://github.com/apache/spark/pull/892#discussion_r14061551
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/TaskSetManager.scala ---
@@ -181,16 +181,14 @@ private[spark] class TaskSetManager(
var
Github user lirui-intel commented on a diff in the pull request:
https://github.com/apache/spark/pull/892#discussion_r14061614
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/TaskSetManager.scala ---
@@ -181,16 +181,14 @@ private[spark] class TaskSetManager(
var
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1178#issuecomment-46809797
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16017/
---
If your
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1178#issuecomment-46809796
Merged build finished. All automated tests passed.
---
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 MLnick commented on the pull request:
https://github.com/apache/spark/pull/455#issuecomment-46810658
hmmm not sure - master built fine for me at the time I posted. Either try
pull again or maybe checkout my branch and try that:
Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/1173#discussion_r14062333
--- Diff:
core/src/main/scala/org/apache/spark/util/logging/RollingFileAppender.scala ---
@@ -83,7 +83,7 @@ private[spark] class RollingFileAppender(
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/1173#discussion_r14062363
--- Diff:
core/src/main/scala/org/apache/spark/util/logging/RollingFileAppender.scala ---
@@ -83,7 +83,7 @@ private[spark] class RollingFileAppender(
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1167#issuecomment-46813830
Merged build finished. All automated tests passed.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1167#issuecomment-46813831
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16018/
---
If your
Github user YanjieGao commented on the pull request:
https://github.com/apache/spark/pull/1151#issuecomment-46814099
Hi all, I have finished this Subtract Operator.
These code can run and pass compile.These code need to be reviewed thanks
a lot!
(1)because there is a
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1099#issuecomment-46814540
Merged build triggered.
---
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 rxin commented on the pull request:
https://github.com/apache/spark/pull/1157#issuecomment-46815231
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
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/1157#issuecomment-46815251
The changes 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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1157#issuecomment-46815303
Merged build triggered.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1157#issuecomment-46815312
Merged build started.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1157#issuecomment-46815429
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16020/
---
If your project is set up for it, you can
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1099#issuecomment-46816642
Merged build finished.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1099#issuecomment-46816645
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16019/
---
If your project is set up for it, you can
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1064#issuecomment-46816812
Merged build started.
---
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 YanjieGao commented on the pull request:
https://github.com/apache/spark/pull/1150#issuecomment-46817079
hi all ,I have finished the INTERSECT operator ,and has update the 6 files
this operator needed .
Now i need your help to review the code .Thanks a lot !
---
If
Github user jerryshao commented on the pull request:
https://github.com/apache/spark/pull/1064#issuecomment-46818315
Hi Matei, I just updated the code according to your comments. For
OrderedRDDFunctions, I only set `KeyOrding` into the shuffle, but not move the
code path, so what's
Github user chenghao-intel commented on a diff in the pull request:
https://github.com/apache/spark/pull/1163#discussion_r14065478
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/plans/logical/LogicalPlan.scala
---
@@ -109,3 +109,12 @@ abstract class UnaryNode
Github user chenghao-intel commented on a diff in the pull request:
https://github.com/apache/spark/pull/1163#discussion_r14065584
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/SparkStrategies.scala ---
@@ -29,6 +29,8 @@ import
Github user chenghao-intel commented on a diff in the pull request:
https://github.com/apache/spark/pull/1163#discussion_r14065703
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/joins.scala ---
@@ -67,73 +62,72 @@ case class HashJoin(
@transient lazy val
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1064#issuecomment-46825394
Merged build finished. All automated tests passed.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1064#issuecomment-46825395
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16021/
---
If your
GitHub user ScrapCodes opened a pull request:
https://github.com/apache/spark/pull/1179
[SPARK-1199][REPL] Remove VALId and use the original import style.
This is an alternate solution.
You can merge this pull request into a Git repository by running:
$ git pull
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1179#issuecomment-46830250
Merged build triggered.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1179#issuecomment-46830261
Merged build started.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1179#issuecomment-46833246
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16022/
---
If your project is set up for it, you can
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1179#issuecomment-46836615
Merged build triggered.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1179#issuecomment-46841280
Merged build finished. All automated tests passed.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1179#issuecomment-46841282
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16023/
---
If your
GitHub user witgo opened a pull request:
https://github.com/apache/spark/pull/1180
[WIP]Spark 2037: yarn client mode doesn't support
spark.yarn.max.executor.failures
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/witgo/spark
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1180#issuecomment-46845264
Merged build triggered.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1180#issuecomment-46845280
Merged build started.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1068#issuecomment-46847056
Merged build triggered.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1068#issuecomment-46847077
Merged build started.
---
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 tgravescs commented on the pull request:
https://github.com/apache/spark/pull/560#issuecomment-46847166
+1 looks good, thanks @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
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/560
---
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 pull request:
https://github.com/apache/spark/pull/1050#issuecomment-46847651
Merged build triggered.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1180#issuecomment-46848316
Merged build triggered.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1180#issuecomment-46848339
Merged build started.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1050#issuecomment-46847666
Merged build started.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1050#issuecomment-46848937
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16026/
---
If your project is set up for it, you can
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1050#issuecomment-46848936
Merged build finished.
---
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 ScrapCodes commented on the pull request:
https://github.com/apache/spark/pull/1050#issuecomment-46849779
I just checked it merges cleanly and still these test failures.
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user ScrapCodes commented on the pull request:
https://github.com/apache/spark/pull/1050#issuecomment-46849805
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
GitHub user mattf opened a pull request:
https://github.com/apache/spark/pull/1181
Fix mvn detection
When mvn is not detected (not in executor's path), 'set -e' causes the
detection to terminate the script before the helpful error message can
be displayed.
You can merge
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1050#issuecomment-46850235
Merged build triggered.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1050#issuecomment-46850255
Merged build started.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1181#issuecomment-46850232
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1180#issuecomment-46850763
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16024/
---
If your
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1180#issuecomment-46850760
Merged build finished. All automated tests passed.
---
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 tgravescs commented on a diff in the pull request:
https://github.com/apache/spark/pull/1112#discussion_r14077635
--- Diff:
yarn/stable/src/main/scala/org/apache/spark/deploy/yarn/ExecutorLauncher.scala
---
@@ -142,9 +149,19 @@ class ExecutorLauncher(args:
Github user tgravescs commented on a diff in the pull request:
https://github.com/apache/spark/pull/1112#discussion_r14077685
--- Diff: core/src/main/scala/org/apache/spark/ui/UIUtils.scala ---
@@ -135,7 +135,16 @@ private[spark] object UIUtils extends Logging {
}
Github user tgravescs commented on a diff in the pull request:
https://github.com/apache/spark/pull/1112#discussion_r14077679
--- Diff: core/src/main/scala/org/apache/spark/ui/JettyUtils.scala ---
@@ -139,7 +139,8 @@ private[spark] object JettyUtils extends Logging {
Github user witgo commented on a diff in the pull request:
https://github.com/apache/spark/pull/1112#discussion_r14077844
--- Diff: core/src/main/scala/org/apache/spark/ui/UIUtils.scala ---
@@ -135,7 +135,16 @@ private[spark] object UIUtils extends Logging {
}
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1068#issuecomment-46852802
Merged build finished. All automated tests passed.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1068#issuecomment-46852803
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16025/
---
If your
Github user tgravescs commented on a diff in the pull request:
https://github.com/apache/spark/pull/1112#discussion_r14077908
--- Diff:
yarn/stable/src/main/scala/org/apache/spark/deploy/yarn/ExecutorLauncher.scala
---
@@ -142,9 +149,19 @@ class ExecutorLauncher(args:
Github user witgo commented on a diff in the pull request:
https://github.com/apache/spark/pull/1112#discussion_r14077980
--- Diff: core/src/main/scala/org/apache/spark/ui/JettyUtils.scala ---
@@ -139,7 +139,8 @@ private[spark] object JettyUtils extends Logging {
/**
Github user tgravescs commented on a diff in the pull request:
https://github.com/apache/spark/pull/1112#discussion_r14078350
--- Diff:
yarn/common/src/main/scala/org/apache/spark/scheduler/cluster/YarnClientSchedulerBackend.scala
---
@@ -116,4 +118,15 @@ private[spark] class
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1180#issuecomment-46854534
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16027/
---
If your
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1180#issuecomment-46854533
Merged build finished. All automated tests passed.
---
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 tgravescs commented on a diff in the pull request:
https://github.com/apache/spark/pull/1112#discussion_r14078643
--- Diff: core/src/main/scala/org/apache/spark/ui/WebUI.scala ---
@@ -43,7 +43,7 @@ private[spark] abstract class WebUI(
extends Logging {
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1050#issuecomment-46855914
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16028/
---
If your project is set up for it, you can
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1050#issuecomment-46855913
Merged build finished.
---
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 tgravescs commented on a diff in the pull request:
https://github.com/apache/spark/pull/1112#discussion_r14079223
--- Diff:
yarn/stable/src/main/scala/org/apache/spark/deploy/yarn/ExecutorLauncher.scala
---
@@ -142,9 +149,19 @@ class ExecutorLauncher(args:
Github user tgravescs commented on a diff in the pull request:
https://github.com/apache/spark/pull/1112#discussion_r14079754
--- Diff:
yarn/common/src/main/scala/org/apache/spark/scheduler/cluster/YarnClientSchedulerBackend.scala
---
@@ -116,4 +118,15 @@ private[spark] class
Github user tgravescs commented on a diff in the pull request:
https://github.com/apache/spark/pull/1112#discussion_r14080191
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/cluster/CoarseGrainedSchedulerBackend.scala
---
@@ -244,6 +247,9 @@ class
Github user tgravescs commented on a diff in the pull request:
https://github.com/apache/spark/pull/1112#discussion_r14080360
--- Diff: core/src/main/scala/org/apache/spark/ui/JettyUtils.scala ---
@@ -139,7 +139,8 @@ private[spark] object JettyUtils extends Logging {
Github user witgo commented on a diff in the pull request:
https://github.com/apache/spark/pull/1112#discussion_r14080567
--- Diff: core/src/main/scala/org/apache/spark/ui/JettyUtils.scala ---
@@ -139,7 +139,8 @@ private[spark] object JettyUtils extends Logging {
/**
Github user willb commented on the pull request:
https://github.com/apache/spark/pull/143#issuecomment-46860741
Can someone take another look at this PR?
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1159#issuecomment-46861976
Build triggered.
---
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 pull request:
https://github.com/apache/spark/pull/1159#issuecomment-46861993
Build started.
---
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 witgo commented on a diff in the pull request:
https://github.com/apache/spark/pull/1112#discussion_r14081769
--- Diff:
yarn/common/src/main/scala/org/apache/spark/scheduler/cluster/YarnClientSchedulerBackend.scala
---
@@ -116,4 +118,15 @@ private[spark] class
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/1158
---
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 tgravescs commented on the pull request:
https://github.com/apache/spark/pull/1159#issuecomment-46864496
thanks for the review. If you have better verbage to use in in the docs
let me know. I need to rebase this to latest master too, which I'll do shortly.
---
If your
Github user koertkuipers commented on the pull request:
https://github.com/apache/spark/pull/735#issuecomment-46865956
not sure if i am supposed to deal with these failures?
On Sat, Jun 21, 2014 at 1:52 PM, UCB AMPLab notificati...@github.com
wrote:
Refer to
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1159#issuecomment-46867543
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16029/
---
If your
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1159#issuecomment-46867542
Build finished. All automated tests 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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1112#issuecomment-46868364
Merged build triggered.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1112#issuecomment-46868383
Merged build started.
---
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 vanzin commented on the pull request:
https://github.com/apache/spark/pull/1094#issuecomment-46869006
@rahulsinghaliitd that bug is about linking to the running web ui of the
driver in yarn-client mode. Slightly different than this one, which is about
setting the link
Github user SpyderRiverA commented on the pull request:
https://github.com/apache/spark/pull/1155#issuecomment-46871874
:+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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1112#issuecomment-46873730
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16030/
---
If your
GitHub user kellrott opened a pull request:
https://github.com/apache/spark/pull/1182
Fix for SPARK-2228
Add check to see if stageId exists in stageIdToPool before attempting to
remove it from poolToActiveStages.
You can merge this pull request into a Git repository by running:
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1182#issuecomment-46877112
Merged build started.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1159#issuecomment-46877100
Merged build triggered.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1159#issuecomment-46877113
Merged build started.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1182#issuecomment-46877098
Merged build triggered.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1183#issuecomment-46879021
Merged build started.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1183#issuecomment-46879005
Merged build triggered.
---
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 andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/1050#issuecomment-46879165
Jenkins, 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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1183#issuecomment-46879649
Merged build triggered.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1183#issuecomment-46879668
Merged build started.
---
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 liancheng opened a pull request:
https://github.com/apache/spark/pull/1183
[SPARK-1669][SQL] Made cacheTable idempotent
JIRA issue: [SPARK-1669](https://issues.apache.org/jira/browse/SPARK-1669)
Caching the same multiple times should end up with only 1
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1050#issuecomment-46879669
Merged build started.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1050#issuecomment-46879650
Merged build triggered.
---
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
1 - 100 of 214 matches
Mail list logo
