Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/156#issuecomment-39499617
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/13731/
---
If your project is set up for it, you can r
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/314#issuecomment-39499618
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/13733/
---
If your project
Github user markhamstra commented on a diff in the pull request:
https://github.com/apache/spark/pull/305#discussion_r11270425
--- Diff:
core/src/test/scala/org/apache/spark/scheduler/DAGSchedulerSuite.scala ---
@@ -323,6 +343,68 @@ class DAGSchedulerSuite extends FunSuite with
Be
Github user pwendell commented on a diff in the pull request:
https://github.com/apache/spark/pull/126#discussion_r11269931
--- Diff:
core/src/main/scala/org/apache/spark/storage/BlockManagerMasterActor.scala ---
@@ -144,6 +155,25 @@ class BlockManagerMasterActor(val isLocal: Boole
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/189#issuecomment-39496205
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. If
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/189#issuecomment-39496207
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/13730/
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/314#issuecomment-39495241
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 have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/314#issuecomment-39495225
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 ha
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/307#issuecomment-39494982
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/13729/
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/307#issuecomment-39494981
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. If
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/295#issuecomment-39494893
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 have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/295#issuecomment-39494895
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/13728/
---
If your project is set up for it, you can r
GitHub user tgravescs opened a pull request:
https://github.com/apache/spark/pull/314
Update documentation for work around for SPARK-1384
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/tgravescs/spark docFix09rc3
Alternatively
Github user pwendell commented on a diff in the pull request:
https://github.com/apache/spark/pull/126#discussion_r11268425
--- Diff:
core/src/main/scala/org/apache/spark/storage/BlockManagerMaster.scala ---
@@ -125,6 +141,34 @@ class BlockManagerMaster(var driverActor: ActorRef,
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/223#issuecomment-39491993
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 have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/223#issuecomment-39491995
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/13732/
---
If your project is set up for it, you can r
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/223#issuecomment-39491883
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 have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/223#issuecomment-39491871
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 ha
Github user mateiz commented on the pull request:
https://github.com/apache/spark/pull/223#issuecomment-39491794
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 have this
Github user pwendell commented on a diff in the pull request:
https://github.com/apache/spark/pull/126#discussion_r11267282
--- Diff: core/src/main/scala/org/apache/spark/scheduler/DAGScheduler.scala
---
@@ -80,13 +80,13 @@ class DAGScheduler(
private[scheduler] def numTotal
Github user mateiz commented on the pull request:
https://github.com/apache/spark/pull/223#issuecomment-39491772
Hey Parviz, FYI, because of the Amazon Software License's restrictions on
Kinesis, it may be difficult to include this in the default build (see
https://issues.apache.org/j
Github user tgravescs commented on the pull request:
https://github.com/apache/spark/pull/303#issuecomment-39491279
From my understanding local: is a spark thing that says the file is on each
worker. This is a bit of an odd usage on yarn. Generally Yarn recommends
sending things with
Github user mateiz commented on a diff in the pull request:
https://github.com/apache/spark/pull/156#discussion_r11266579
--- Diff: core/src/main/scala/org/apache/spark/rdd/RDD.scala ---
@@ -664,6 +664,24 @@ abstract class RDD[T: ClassTag](
}
/**
+ * Return
Github user pwendell commented on a diff in the pull request:
https://github.com/apache/spark/pull/126#discussion_r11266861
--- Diff: core/src/main/scala/org/apache/spark/broadcast/Broadcast.scala ---
@@ -51,49 +50,37 @@ import org.apache.spark._
* @tparam T Type of the data c
Github user pwendell commented on a diff in the pull request:
https://github.com/apache/spark/pull/126#discussion_r11266739
--- Diff: core/src/main/scala/org/apache/spark/broadcast/Broadcast.scala ---
@@ -51,49 +50,37 @@ import org.apache.spark._
* @tparam T Type of the data c
Github user markhamstra commented on the pull request:
https://github.com/apache/spark/pull/288#issuecomment-39490098
Really, there should be no need for that. Just do a 'pull --rebase' in
your branch and everything that is not already part of master will be moved
to after mast
Github user tgravescs commented on the pull request:
https://github.com/apache/spark/pull/128#issuecomment-39490166
Ok, thanks for the heads up, I hope to get to it today or tomorrow.
---
If your project is set up for it, you can reply to this email and have your
reply appear on Git
Github user mateiz commented on the pull request:
https://github.com/apache/spark/pull/156#issuecomment-39490196
Made some more comments to simplify this now that we return an Iterator.
---
If your project is set up for it, you can reply to this email and have your
reply appear on Git
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/248#issuecomment-39490052
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. If
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/248#issuecomment-39490054
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/13727/
---
If your project
Github user willb commented on the pull request:
https://github.com/apache/spark/pull/189#issuecomment-39490073
Thanks for taking another look, Matei! I know there's a lot of stuff to
get in before the merge window closes and appreciate the update.
---
If your project is set up for
Github user mateiz commented on the pull request:
https://github.com/apache/spark/pull/189#issuecomment-39489148
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 have this
Github user pwendell commented on a diff in the pull request:
https://github.com/apache/spark/pull/126#discussion_r11266501
--- Diff: core/src/main/scala/org/apache/spark/SparkEnv.scala ---
@@ -180,12 +180,24 @@ object SparkEnv extends Logging {
}
}
+
Github user mateiz commented on a diff in the pull request:
https://github.com/apache/spark/pull/156#discussion_r11266448
--- Diff: core/src/main/scala/org/apache/spark/rdd/RDD.scala ---
@@ -664,6 +664,24 @@ abstract class RDD[T: ClassTag](
}
/**
+ * Return
Github user velvia commented on the pull request:
https://github.com/apache/spark/pull/288#issuecomment-39489767
Mark, thanks. Yeah, I realize instead of doing a merge I should just do a
pull now, but it's probably too late for this PR. Instead I'll close it
and reopen and squ
Github user mateiz commented on a diff in the pull request:
https://github.com/apache/spark/pull/156#discussion_r11266352
--- Diff: core/src/main/scala/org/apache/spark/rdd/RDD.scala ---
@@ -664,6 +664,24 @@ abstract class RDD[T: ClassTag](
}
/**
+ * Return
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/189#issuecomment-39489550
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 ha
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/156#issuecomment-39489554
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 ha
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/156#issuecomment-39489572
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 have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/189#issuecomment-39489560
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 have
Github user mateiz commented on a diff in the pull request:
https://github.com/apache/spark/pull/156#discussion_r11266266
--- Diff: core/src/main/scala/org/apache/spark/rdd/RDD.scala ---
@@ -664,6 +664,24 @@ abstract class RDD[T: ClassTag](
}
/**
+ * Return
Github user mateiz commented on a diff in the pull request:
https://github.com/apache/spark/pull/156#discussion_r11266262
--- Diff: core/src/main/scala/org/apache/spark/api/java/JavaRDDLike.scala
---
@@ -282,6 +283,17 @@ trait JavaRDDLike[T, This <: JavaRDDLike[T, This]]
extends S
Github user tgravescs commented on a diff in the pull request:
https://github.com/apache/spark/pull/303#discussion_r11266231
--- Diff:
yarn/common/src/main/scala/org/apache/spark/deploy/yarn/ClientBase.scala ---
@@ -427,28 +430,49 @@ object ClientBase {
}
def po
Github user mateiz commented on the pull request:
https://github.com/apache/spark/pull/156#issuecomment-39489375
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 have this
Github user mateiz commented on the pull request:
https://github.com/apache/spark/pull/189#issuecomment-39489309
Hey Will, sorry for the really late reply, still interested in having this
go in, at least with the simple version. I've just been swamped with other
reviews.
---
If your
Github user mateiz commented on the pull request:
https://github.com/apache/spark/pull/128#issuecomment-39489093
BTW if you want this to go to 1.0, it would be good to make these changes
soon. We can potentially also include it without Windows support, and mark the
folder stuff as exp
Github user tgravescs commented on a diff in the pull request:
https://github.com/apache/spark/pull/303#discussion_r11265870
--- Diff:
yarn/common/src/main/scala/org/apache/spark/deploy/yarn/ClientBase.scala ---
@@ -427,28 +430,49 @@ object ClientBase {
}
def po
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/307#issuecomment-39488315
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 ha
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/307#issuecomment-39488330
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 have
Github user tgravescs commented on the pull request:
https://github.com/apache/spark/pull/313#issuecomment-39488004
Change looks good to me. Will wait to see if anyone else has comments.
---
If your project is set up for it, you can reply to this email and have your
reply appear on G
Github user pwendell commented on a diff in the pull request:
https://github.com/apache/spark/pull/126#discussion_r11265542
--- Diff: core/src/main/scala/org/apache/spark/SparkContext.scala ---
@@ -641,7 +643,11 @@ class SparkContext(
* [[org.apache.spark.broadcast.Broadcast
Github user pwendell commented on a diff in the pull request:
https://github.com/apache/spark/pull/126#discussion_r11265456
--- Diff:
core/src/main/scala/org/apache/spark/broadcast/HttpBroadcast.scala ---
@@ -183,20 +197,48 @@ private object HttpBroadcast extends Logging {
Github user markhamstra commented on the pull request:
https://github.com/apache/spark/pull/307#issuecomment-39486891
Looks like just removing the findbugs jsr305 dependency entirely works
fine, but bumping the Guava version not so much. I'm going to change the name
of this JIRA and
Github user mateiz commented on a diff in the pull request:
https://github.com/apache/spark/pull/158#discussion_r11264777
--- Diff: core/src/main/scala/org/apache/spark/storage/BlockManager.scala
---
@@ -669,7 +717,7 @@ private[spark] class BlockManager(
// Either we
Github user markhamstra commented on the pull request:
https://github.com/apache/spark/pull/288#issuecomment-39485564
Rebasing is no big deal if the commits that you are rebasing are only in a
private repo. For example, even though https://github.com/markhamstra/spark is
technically
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/313#issuecomment-39485509
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/13726/
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/313#issuecomment-39485508
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. If
Github user pwendell commented on a diff in the pull request:
https://github.com/apache/spark/pull/126#discussion_r11264351
--- Diff: core/src/main/scala/org/apache/spark/MapOutputTracker.scala ---
@@ -194,17 +194,43 @@ private[spark] class MapOutputTracker(conf:
SparkConf) extends
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/295#issuecomment-39484062
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 have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/295#issuecomment-39484050
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 ha
Github user pwendell commented on a diff in the pull request:
https://github.com/apache/spark/pull/126#discussion_r11264135
--- Diff: core/src/main/scala/org/apache/spark/MapOutputTracker.scala ---
@@ -65,26 +65,36 @@ private[spark] class
MapOutputTrackerMasterActor(tracker: MapOut
Github user pwendell commented on a diff in the pull request:
https://github.com/apache/spark/pull/126#discussion_r11263980
--- Diff: core/src/main/scala/org/apache/spark/ContextCleaner.scala ---
@@ -0,0 +1,196 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) unde
Github user marmbrus commented on the pull request:
https://github.com/apache/spark/pull/295#issuecomment-39483627
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 have t
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/248#issuecomment-39483451
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 ha
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/248#issuecomment-39483466
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 have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/310#issuecomment-39483328
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. If
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/310#issuecomment-39483329
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/13725/
---
If your project
Github user pwendell commented on a diff in the pull request:
https://github.com/apache/spark/pull/126#discussion_r11263798
--- Diff: core/src/main/scala/org/apache/spark/ContextCleaner.scala ---
@@ -0,0 +1,196 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) unde
Github user marmbrus commented on the pull request:
https://github.com/apache/spark/pull/275#issuecomment-39483020
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 have t
Github user aarondav commented on the pull request:
https://github.com/apache/spark/pull/288#issuecomment-39482892
rebasing and then force pushing isn't kind to Git, but GitHub does handle
it well.
---
If your project is set up for it, you can reply to this email and have your
reply
Github user marmbrus commented on the pull request:
https://github.com/apache/spark/pull/248#issuecomment-39482957
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 have t
Github user pwendell commented on a diff in the pull request:
https://github.com/apache/spark/pull/126#discussion_r11263323
--- Diff: core/src/main/scala/org/apache/spark/ContextCleaner.scala ---
@@ -0,0 +1,196 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) unde
Github user pwendell commented on a diff in the pull request:
https://github.com/apache/spark/pull/126#discussion_r11263287
--- Diff: core/src/main/scala/org/apache/spark/ContextCleaner.scala ---
@@ -0,0 +1,196 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) unde
Github user pwendell commented on a diff in the pull request:
https://github.com/apache/spark/pull/126#discussion_r11263139
--- Diff: core/src/main/scala/org/apache/spark/ContextCleaner.scala ---
@@ -0,0 +1,196 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) unde
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/288#issuecomment-39481008
@velvia what happens if you just close and re-open the pull request? Will
that work?
---
If your project is set up for it, you can reply to this email and have your
repl
Github user pwendell commented on a diff in the pull request:
https://github.com/apache/spark/pull/204#discussion_r11262132
--- Diff:
core/src/main/scala/org/apache/spark/deploy/history/HistoryServer.scala ---
@@ -0,0 +1,221 @@
+/*
+ * Licensed to the Apache Software Founda
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/313#issuecomment-39478612
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 have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/313#issuecomment-39478597
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 ha
GitHub user sryza opened a pull request:
https://github.com/apache/spark/pull/313
SPARK-1350. Always use JAVA_HOME to run executor container JVMs.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/sryza/spark sandy-spark-1350
Alte
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/310#issuecomment-39476959
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 have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/310#issuecomment-39476946
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 ha
Github user aarondav commented on a diff in the pull request:
https://github.com/apache/spark/pull/310#discussion_r11261202
--- Diff: bin/spark-shell ---
@@ -145,7 +145,7 @@ function resolve_spark_master(){
fi
if [ -z "$MASTER" ]; then
-MASTER="$D
Github user tgravescs commented on a diff in the pull request:
https://github.com/apache/spark/pull/204#discussion_r11256259
--- Diff:
core/src/main/scala/org/apache/spark/deploy/history/HistoryServer.scala ---
@@ -0,0 +1,221 @@
+/*
+ * Licensed to the Apache Software Found
Github user tgravescs commented on a diff in the pull request:
https://github.com/apache/spark/pull/204#discussion_r11256081
--- Diff:
core/src/main/scala/org/apache/spark/deploy/history/HistoryServer.scala ---
@@ -0,0 +1,221 @@
+/*
+ * Licensed to the Apache Software Found
Github user tgravescs commented on a diff in the pull request:
https://github.com/apache/spark/pull/204#discussion_r11254543
--- Diff: sbin/start-history-server.sh ---
@@ -0,0 +1,46 @@
+#!/usr/bin/env bash
+
+#
+# Licensed to the Apache Software Foundation (ASF) unde
Github user tgravescs commented on a diff in the pull request:
https://github.com/apache/spark/pull/204#discussion_r11254082
--- Diff:
core/src/main/scala/org/apache/spark/deploy/history/HistoryServer.scala ---
@@ -0,0 +1,221 @@
+/*
+ * Licensed to the Apache Software Found
Github user tgravescs commented on a diff in the pull request:
https://github.com/apache/spark/pull/204#discussion_r11253731
--- Diff:
core/src/main/scala/org/apache/spark/deploy/history/HistoryServer.scala ---
@@ -0,0 +1,221 @@
+/*
+ * Licensed to the Apache Software Found
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/195#issuecomment-39457183
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/13724/
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/195#issuecomment-39457180
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. If
Github user AndreSchumacher commented on the pull request:
https://github.com/apache/spark/pull/195#issuecomment-39457091
@marmbrus Thanks again for the comments and changes. I shuffled the imports
and removed the additions to SQLContext. Also moved the insert examples to the
tests ra
Github user tgravescs commented on the pull request:
https://github.com/apache/spark/pull/204#issuecomment-39454420
First of all I would like to say great work, having this history server is
awesome!!
I'm trying it out on a non-secure yarn cluster but when I run something
tha
Github user tgravescs commented on the pull request:
https://github.com/apache/spark/pull/204#issuecomment-39453542
Also to clarify that the history files are actually first written to the
users staging directory, which is only user readable/writable, and then moved
over to done_inter
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/195#issuecomment-39450885
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 ha
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/195#issuecomment-39450898
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 have
Github user tgravescs commented on the pull request:
https://github.com/apache/spark/pull/204#issuecomment-39449932
Its not readable by other users in the intermediate directory. Sorry I
didn't explain fully. That directory itself is 1777, sticky bit set, world
writable. Each user
Github user ueshin commented on a diff in the pull request:
https://github.com/apache/spark/pull/310#discussion_r11246612
--- Diff: bin/spark-shell ---
@@ -145,7 +145,7 @@ function resolve_spark_master(){
fi
if [ -z "$MASTER" ]; then
-MASTER="$DEF
Github user scwf commented on the pull request:
https://github.com/apache/spark/pull/312#issuecomment-39434966
i am wrong, i think this is an order issue, it is a matter of the order of
starting of ui and the taskScheduler in sc
---
If your project is set up for it, you can reply to
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/268#issuecomment-39432280
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 p
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/268#issuecomment-39432281
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/13723/
---
If your project
Github user scwf commented on the pull request:
https://github.com/apache/spark/pull/312#issuecomment-39431524
TaskSchedulerImpl should override rootPool method
---
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
201 - 300 of 329 matches
Mail list logo
