Github user markhamstra commented on the pull request:
https://github.com/apache/spark/pull/2014#issuecomment-55609759
There really should be at least some mention of zinc
(https://github.com/typesafehub/zinc) in our maven build instructions, since
using zinc greatly improves
Github user markhamstra commented on the pull request:
https://github.com/apache/spark/pull/2014#issuecomment-55611558
Yes, I know that the scala-maven-plugin will throw warnings if zinc isn't
being used. I also know that many users are either confused by those warnings
or ignore
Github user markhamstra commented on a diff in the pull request:
https://github.com/apache/spark/pull/2014#discussion_r17570971
--- Diff: docs/building-spark.md ---
@@ -159,4 +160,21 @@ then ship it over to the cluster. We are investigating
the exact cause
Github user markhamstra commented on a diff in the pull request:
https://github.com/apache/spark/pull/2447#discussion_r17741897
--- Diff: core/src/main/scala/org/apache/spark/rdd/RDD.scala ---
@@ -208,6 +208,23 @@ abstract class RDD[T: ClassTag
Github user markhamstra commented on the pull request:
https://github.com/apache/spark/pull/2482#issuecomment-56310103
+1 @rxin
Just scanned through the code quickly, and I didn't immediately see
anything that would preclude retaining and deprecating the old code while
Github user markhamstra commented on the pull request:
https://github.com/apache/spark/pull/1689#issuecomment-57043930
Have either of you thought about how to coordinate this with Josh's work on
SPARK-3626? https://github.com/apache/spark/pull/2482
---
If your project is set up
Github user markhamstra commented on a diff in the pull request:
https://github.com/apache/spark/pull/2470#discussion_r18136843
--- Diff: core/src/main/scala/org/apache/spark/scheduler/MapStatus.scala ---
@@ -24,22 +24,123 @@ import org.apache.spark.storage.BlockManagerId
Github user markhamstra commented on a diff in the pull request:
https://github.com/apache/spark/pull/2524#discussion_r18193968
--- Diff: core/src/main/scala/org/apache/spark/scheduler/DAGScheduler.scala
---
@@ -112,6 +112,10 @@ class DAGScheduler(
// stray messages
Github user markhamstra commented on a diff in the pull request:
https://github.com/apache/spark/pull/1525#discussion_r15240513
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/cluster/CoarseGrainedSchedulerBackend.scala
---
@@ -47,19 +47,19 @@ class
Github user markhamstra commented on a diff in the pull request:
https://github.com/apache/spark/pull/1525#discussion_r15242266
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/cluster/SparkDeploySchedulerBackend.scala
---
@@ -108,4 +108,8 @@ private[spark] class
Github user markhamstra commented on a diff in the pull request:
https://github.com/apache/spark/pull/1525#discussion_r15242315
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/cluster/SparkDeploySchedulerBackend.scala
---
@@ -108,4 +108,8 @@ private[spark] class
Github user markhamstra commented on the pull request:
https://github.com/apache/spark/pull/1418#issuecomment-49773532
ok to 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
Github user markhamstra commented on a diff in the pull request:
https://github.com/apache/spark/pull/1528#discussion_r15246213
--- Diff: core/src/main/scala/org/apache/spark/scheduler/DAGScheduler.scala
---
@@ -778,8 +778,10 @@ class DAGScheduler(
logInfo(Submitting
Github user markhamstra commented on a diff in the pull request:
https://github.com/apache/spark/pull/1528#discussion_r15248491
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/SchedulingAlgorithm.scala ---
@@ -32,11 +32,21 @@ private[spark] class FIFOSchedulingAlgorithm
Github user markhamstra commented on a diff in the pull request:
https://github.com/apache/spark/pull/1535#discussion_r15258957
--- Diff: core/src/main/scala/org/apache/spark/rdd/RDD.scala ---
@@ -1294,7 +1307,11 @@ abstract class RDD[T: ClassTag](
val partitionStr
Github user markhamstra commented on a diff in the pull request:
https://github.com/apache/spark/pull/1525#discussion_r15268935
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/cluster/CoarseGrainedSchedulerBackend.scala
---
@@ -47,19 +47,19 @@ class
Github user markhamstra commented on a diff in the pull request:
https://github.com/apache/spark/pull/1528#discussion_r15270158
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/SchedulingAlgorithm.scala ---
@@ -17,6 +17,8 @@
package org.apache.spark.scheduler
Github user markhamstra commented on a diff in the pull request:
https://github.com/apache/spark/pull/1528#discussion_r15270239
--- Diff: core/src/main/scala/org/apache/spark/scheduler/TaskSet.scala ---
@@ -27,9 +27,18 @@ private[spark] class TaskSet(
val tasks: Array[Task
Github user markhamstra commented on a diff in the pull request:
https://github.com/apache/spark/pull/1525#discussion_r15270679
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/cluster/CoarseGrainedSchedulerBackend.scala
---
@@ -47,19 +47,19 @@ class
Github user markhamstra commented on a diff in the pull request:
https://github.com/apache/spark/pull/1525#discussion_r15270909
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/cluster/CoarseGrainedSchedulerBackend.scala
---
@@ -47,19 +47,19 @@ class
Github user markhamstra commented on a diff in the pull request:
https://github.com/apache/spark/pull/1528#discussion_r15272274
--- Diff: core/src/main/scala/org/apache/spark/scheduler/TaskSet.scala ---
@@ -27,9 +27,18 @@ private[spark] class TaskSet(
val tasks: Array[Task
Github user markhamstra commented on a diff in the pull request:
https://github.com/apache/spark/pull/1525#discussion_r15272634
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/cluster/CoarseGrainedSchedulerBackend.scala
---
@@ -268,14 +264,18 @@ class
Github user markhamstra commented on the pull request:
https://github.com/apache/spark/pull/1528#issuecomment-49848091
This looks like a clean implementation, but you still need to open a JIRA
issue to explain why you want this; then edit the description of this PR to
reference
Github user markhamstra commented on the pull request:
https://github.com/apache/spark/pull/1528#issuecomment-49848309
Sorry, looks like you already have SPARK-2618, so change change the title
of this PR to include that.
---
If your project is set up for it, you can reply
Github user markhamstra commented on the pull request:
https://github.com/apache/spark/pull/1535#issuecomment-49874874
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
Github user markhamstra commented on a diff in the pull request:
https://github.com/apache/spark/pull/1548#discussion_r15289573
--- Diff: core/src/main/scala/org/apache/spark/scheduler/DAGScheduler.scala
---
@@ -1202,8 +1202,12 @@ private[scheduler] class
Github user markhamstra commented on the pull request:
https://github.com/apache/spark/pull/1516#issuecomment-49911032
This appears to be a reversion of d58502a1562bbfb1bb4e517ebcc8239efd639297
while ignoring and misapplying the comment regarding ordering (which I'm not
completely
Github user markhamstra commented on the pull request:
https://github.com/apache/spark/pull/1528#issuecomment-49916553
Yeah, I'm wondering whether the actual problem is that creation and use of
scheduler pools with different weights is unclear or too difficult; and that if
we could
Github user markhamstra commented on a diff in the pull request:
https://github.com/apache/spark/pull/1561#discussion_r15327897
--- Diff: core/src/main/scala/org/apache/spark/scheduler/Stage.scala ---
@@ -56,6 +58,16 @@ private[spark] class Stage(
val numPartitions
Github user markhamstra commented on a diff in the pull request:
https://github.com/apache/spark/pull/1561#discussion_r15328234
--- Diff: core/src/main/scala/org/apache/spark/scheduler/DAGScheduler.scala
---
@@ -315,13 +309,14 @@ class DAGScheduler(
*/
private def
Github user markhamstra commented on a diff in the pull request:
https://github.com/apache/spark/pull/1561#discussion_r15328329
--- Diff: core/src/main/scala/org/apache/spark/scheduler/DAGScheduler.scala
---
@@ -315,13 +309,14 @@ class DAGScheduler(
*/
private def
Github user markhamstra commented on a diff in the pull request:
https://github.com/apache/spark/pull/1561#discussion_r15328468
--- Diff: core/src/main/scala/org/apache/spark/scheduler/DAGScheduler.scala
---
@@ -341,8 +336,9 @@ class DAGScheduler
Github user markhamstra commented on a diff in the pull request:
https://github.com/apache/spark/pull/1561#discussion_r15328544
--- Diff: core/src/main/scala/org/apache/spark/scheduler/DAGScheduler.scala
---
@@ -341,8 +336,9 @@ class DAGScheduler
Github user markhamstra commented on a diff in the pull request:
https://github.com/apache/spark/pull/1561#discussion_r15328773
--- Diff: core/src/main/scala/org/apache/spark/scheduler/DAGScheduler.scala
---
@@ -992,13 +974,14 @@ class DAGScheduler(
}
private
Github user markhamstra commented on the pull request:
https://github.com/apache/spark/pull/1561#issuecomment-49967238
JIRA?
---
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 markhamstra commented on the pull request:
https://github.com/apache/spark/pull/1566#issuecomment-49968268
Makes sense. 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
Github user markhamstra commented on a diff in the pull request:
https://github.com/apache/spark/pull/1561#discussion_r15331775
--- Diff: core/src/main/scala/org/apache/spark/scheduler/DAGScheduler.scala
---
@@ -355,14 +351,13 @@ class DAGScheduler(
logDebug
Github user markhamstra commented on a diff in the pull request:
https://github.com/apache/spark/pull/1561#discussion_r15331819
--- Diff: core/src/main/scala/org/apache/spark/scheduler/Stage.scala ---
@@ -22,6 +22,8 @@ import org.apache.spark.rdd.RDD
import
Github user markhamstra commented on a diff in the pull request:
https://github.com/apache/spark/pull/1561#discussion_r15332026
--- Diff: core/src/main/scala/org/apache/spark/scheduler/Stage.scala ---
@@ -56,6 +58,16 @@ private[spark] class Stage(
val numPartitions
Github user markhamstra commented on a diff in the pull request:
https://github.com/apache/spark/pull/993#discussion_r15334407
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/codegen/CodeGenerator.scala
---
@@ -0,0 +1,458
Github user markhamstra commented on a diff in the pull request:
https://github.com/apache/spark/pull/1561#discussion_r15356652
--- Diff: core/src/main/scala/org/apache/spark/scheduler/DAGScheduler.scala
---
@@ -341,8 +336,9 @@ class DAGScheduler
Github user markhamstra commented on a diff in the pull request:
https://github.com/apache/spark/pull/1561#discussion_r15361883
--- Diff: core/src/main/scala/org/apache/spark/scheduler/DAGScheduler.scala
---
@@ -341,8 +336,9 @@ class DAGScheduler
Github user markhamstra commented on the pull request:
https://github.com/apache/spark/pull/637#issuecomment-50057749
This rebases cleanly on top of https://github.com/apache/spark/pull/1561,
so let's get that one in first.
---
If your project is set up for it, you can reply
Github user markhamstra commented on the pull request:
https://github.com/apache/spark/pull/1583#issuecomment-50105915
Does anyone recall why we lost the closure cleaning in
https://github.com/apache/spark/commit/6b288b75d4c05f42ad3612813dc77ff824bb6203
?
---
If your project is set
Github user markhamstra commented on the pull request:
https://github.com/apache/spark/pull/1499#issuecomment-50160338
After installing `hub` you can also do a bunch of new stuff on the command
line, including `hub checkout https://github.com/apache/spark/pull/1499`
https
Github user markhamstra commented on the pull request:
https://github.com/apache/spark/pull/1548#issuecomment-50174114
@YanTangZhai If you are searching for another solution and abandoning this
PR, could you please close this PR and open a new one when you have something
different
Github user markhamstra commented on the pull request:
https://github.com/apache/spark/pull/1561#issuecomment-50201015
@JoshRosen Why a trait instead of an abstract class? We're not expecting
to need to mixin Stage outside of the Stage class hierarchy, right?
---
If your project
Github user markhamstra commented on a diff in the pull request:
https://github.com/apache/spark/pull/1607#discussion_r15437121
--- Diff:
core/src/main/scala/org/apache/spark/util/collection/ExternalAppendOnlyMap.scala
---
@@ -110,42 +110,56 @@ class ExternalAppendOnlyMap[K, V, C
Github user markhamstra commented on a diff in the pull request:
https://github.com/apache/spark/pull/1607#discussion_r15439805
--- Diff:
core/src/main/scala/org/apache/spark/util/collection/ExternalAppendOnlyMap.scala
---
@@ -110,42 +110,56 @@ class ExternalAppendOnlyMap[K, V, C
Github user markhamstra commented on a diff in the pull request:
https://github.com/apache/spark/pull/1562#discussion_r15439847
--- Diff: core/src/main/scala/org/apache/spark/Partitioner.scala ---
@@ -105,24 +108,91 @@ class RangePartitioner[K : Ordering : ClassTag, V
Github user markhamstra commented on the pull request:
https://github.com/apache/spark/pull/1360#issuecomment-50281668
ping
Probably too late for a 1.0.2-rc, but this should go into 1.0.3 and 1.1.0.
---
If your project is set up for it, you can reply to this email and have
Github user markhamstra commented on a diff in the pull request:
https://github.com/apache/spark/pull/1611#discussion_r15442657
--- Diff: assembly/src/deb/control/examples/control ---
@@ -0,0 +1,8 @@
+Package: [[deb.pkg.name]]-examples
+Version: [[version]]-[[buildNumber
Github user markhamstra commented on a diff in the pull request:
https://github.com/apache/spark/pull/1498#discussion_r15498156
--- Diff: core/src/main/scala/org/apache/spark/scheduler/DAGScheduler.scala
---
@@ -17,7 +17,7 @@
package org.apache.spark.scheduler
Github user markhamstra commented on a diff in the pull request:
https://github.com/apache/spark/pull/1498#discussion_r15499105
--- Diff: core/src/main/scala/org/apache/spark/scheduler/DAGScheduler.scala
---
@@ -691,25 +689,41 @@ class DAGScheduler
Github user markhamstra commented on a diff in the pull request:
https://github.com/apache/spark/pull/1056#discussion_r15538656
--- Diff: core/src/main/scala/org/apache/spark/HeartbeatReceiver.scala ---
@@ -0,0 +1,47 @@
+/*
+ * Licensed to the Apache Software Foundation
Github user markhamstra commented on the pull request:
https://github.com/apache/spark/pull/1542#issuecomment-50511022
I dunno, merging a PR with no changed files doesn't sound too scary to me.
Something is definitely messed up in this PR, with both `Commits` and
`Files
Github user markhamstra commented on a diff in the pull request:
https://github.com/apache/spark/pull/1056#discussion_r15542781
--- Diff: core/src/main/scala/org/apache/spark/executor/Executor.scala ---
@@ -348,4 +353,48 @@ private[spark] class Executor
Github user markhamstra commented on a diff in the pull request:
https://github.com/apache/spark/pull/1056#discussion_r15543587
--- Diff: core/src/main/scala/org/apache/spark/scheduler/DAGScheduler.scala
---
@@ -38,8 +37,10 @@ import org.apache.spark._
import
Github user markhamstra commented on a diff in the pull request:
https://github.com/apache/spark/pull/1309#discussion_r15557746
--- Diff: core/src/main/scala/org/apache/spark/scheduler/DAGScheduler.scala
---
@@ -809,12 +810,25 @@ class DAGScheduler(
listenerBus.post
Github user markhamstra commented on the pull request:
https://github.com/apache/spark/pull/1617#issuecomment-50552553
What is the need to expose the jobId after the job is finished?
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user markhamstra commented on a diff in the pull request:
https://github.com/apache/spark/pull/1056#discussion_r15559948
--- Diff: core/src/main/scala/org/apache/spark/executor/Executor.scala ---
@@ -348,4 +353,48 @@ private[spark] class Executor
Github user markhamstra commented on a diff in the pull request:
https://github.com/apache/spark/pull/1056#discussion_r15560393
--- Diff: core/src/main/scala/org/apache/spark/executor/Executor.scala ---
@@ -348,4 +353,48 @@ private[spark] class Executor
Github user markhamstra commented on a diff in the pull request:
https://github.com/apache/spark/pull/996#discussion_r15702768
--- Diff: assembly/pom.xml ---
@@ -26,7 +26,7 @@
/parent
groupIdorg.apache.spark/groupId
- artifactIdspark-assembly_2.10
Github user markhamstra commented on a diff in the pull request:
https://github.com/apache/spark/pull/996#discussion_r15743162
--- Diff: assembly/pom.xml ---
@@ -26,7 +26,7 @@
/parent
groupIdorg.apache.spark/groupId
- artifactIdspark-assembly_2.10
Github user markhamstra commented on a diff in the pull request:
https://github.com/apache/spark/pull/996#discussion_r15770288
--- Diff: assembly/pom.xml ---
@@ -26,7 +26,7 @@
/parent
groupIdorg.apache.spark/groupId
- artifactIdspark-assembly_2.10
Github user markhamstra commented on the pull request:
https://github.com/apache/spark/pull/1751#issuecomment-51257040
@tdas @pwendell This broke the Maven build:
```
~/Apache/spark(branch-1.1|â) ⤠mvn -U -DskipTests clean install
.
.
.
[error]
Apache/spark
Github user markhamstra commented on a diff in the pull request:
https://github.com/apache/spark/pull/1836#discussion_r16006978
--- Diff:
core/src/main/scala/org/apache/spark/broadcast/TorrentBroadcast.scala ---
@@ -17,14 +17,14 @@
package org.apache.spark.broadcast
Github user markhamstra commented on a diff in the pull request:
https://github.com/apache/spark/pull/1810#discussion_r16028829
--- Diff: core/src/main/scala/org/apache/spark/SparkEnv.scala ---
@@ -146,9 +146,9 @@ object SparkEnv extends Logging {
}
val
Github user markhamstra commented on the pull request:
https://github.com/apache/spark/pull/1031#issuecomment-51945400
It's definitely not cross-platform.
---
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 markhamstra commented on the pull request:
https://github.com/apache/spark/pull/1360#issuecomment-51959659
@pwendell Still should go into 1.1.0... The change is fairly small, and
the unpatched behavior is pretty nasty for long-running applications.
---
If your project
Github user markhamstra commented on the pull request:
https://github.com/apache/spark/pull/1908#issuecomment-51962565
nit: That's not really an adequate title for this PR, Ameet. It should
include enough description so that we can tell what it is about in the
corresponding subject
Github user markhamstra commented on the pull request:
https://github.com/apache/spark/pull/1909#issuecomment-51965072
Erik, you've been doing some great work on making non-lazy transforms lazy!
I haven't had time to thoroughly review your recent PRs, but can you do some
checks
Github user markhamstra commented on the pull request:
https://github.com/apache/spark/pull/2477#issuecomment-58293963
This certainly works, but I'm not sure that we need to maintain the
complexity of having both a `jars` directory and a `lib` symlink to it. What
we want
Github user markhamstra commented on a diff in the pull request:
https://github.com/apache/spark/pull/2795#discussion_r18861574
--- Diff: core/src/main/scala/org/apache/spark/util/Utils.scala ---
@@ -340,8 +340,8 @@ private[spark] object Utils extends Logging {
val
Github user markhamstra commented on the pull request:
https://github.com/apache/spark/pull/2810#issuecomment-59223588
ok to 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
Github user markhamstra commented on the pull request:
https://github.com/apache/spark/pull/2810#issuecomment-59400293
Yup, LGTM. And as a general rule for the future, avoid pattern matching on
Some and None. In most cases you should instead use a map, flatMap or foreach
over
Github user markhamstra commented on a diff in the pull request:
https://github.com/apache/spark/pull/2828#discussion_r18985880
--- Diff: core/src/main/scala/org/apache/spark/deploy/worker/Worker.scala
---
@@ -243,6 +249,10 @@ private[spark] class Worker(
System.exit
Github user markhamstra commented on the pull request:
https://github.com/apache/spark/pull/2828#issuecomment-59810037
@CodingCat, Worker is private[spark], so what is the nature of your
concern? In fact, I'm wondering whether we really want the changes in this PR
that make some
Github user markhamstra commented on the pull request:
https://github.com/apache/spark/pull/2828#issuecomment-59811803
A legitimate concern, and certainly something that could be worked up into
a JIRA issue and separate pull request. But it's not a very pressing issue
since nothing
Github user markhamstra commented on the pull request:
https://github.com/apache/spark/pull/1078#issuecomment-46071589
FYI Bumping all the way to the current scalatest 2.2.0 also works.
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user markhamstra commented on the pull request:
https://github.com/apache/spark/pull/637#issuecomment-46104906
It means that the check for binary compatibility after your patch is
applied has failed because the checker thinks that there previously was a
default/automatic
GitHub user markhamstra opened a pull request:
https://github.com/apache/spark/pull/1100
SPARK-2158 Clean up core/stdout file from FileAppenderSuite
@tdas
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/markhamstra/spark SPARK
Github user markhamstra commented on the pull request:
https://github.com/apache/spark/pull/1100#issuecomment-46265806
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
Github user markhamstra commented on the pull request:
https://github.com/apache/spark/pull/999#issuecomment-46389597
Is that the basic strategy we are going to use with AlphaComponents --
merging new APIs at both the minor and maintenance levels? I don't know that I
have any
Github user markhamstra commented on the pull request:
https://github.com/apache/spark/pull/999#issuecomment-46436035
Hmmm, that doesn't precisely match my recollection or understanding.
Certainly we discussed that alpha components aren't required to maintain a
stable API, but I
Github user markhamstra commented on the pull request:
https://github.com/apache/spark/pull/1115#issuecomment-46479466
Yes, this PR is not in a useful state right now. It's hard to even find
the proposed changes because of all the clutter of unnecessary commits, but it
looks to me
Github user markhamstra commented on the pull request:
https://github.com/apache/spark/pull/686#issuecomment-46684950
ping: This should go into 1.0.1
@pwendell
---
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 markhamstra commented on a diff in the pull request:
https://github.com/apache/spark/pull/686#discussion_r14032954
--- Diff:
core/src/test/scala/org/apache/spark/scheduler/DAGSchedulerSuite.scala ---
@@ -313,6 +314,47 @@ class DAGSchedulerSuite extends
TestKit
Github user markhamstra commented on a diff in the pull request:
https://github.com/apache/spark/pull/686#discussion_r14040631
--- Diff: core/src/main/scala/org/apache/spark/scheduler/DAGScheduler.scala
---
@@ -1062,10 +1062,15 @@ class DAGScheduler
Github user markhamstra commented on a diff in the pull request:
https://github.com/apache/spark/pull/686#discussion_r14041296
--- Diff: core/src/main/scala/org/apache/spark/scheduler/DAGScheduler.scala
---
@@ -1062,10 +1062,15 @@ class DAGScheduler
Github user markhamstra commented on a diff in the pull request:
https://github.com/apache/spark/pull/686#discussion_r14041700
--- Diff: core/src/main/scala/org/apache/spark/scheduler/DAGScheduler.scala
---
@@ -1062,10 +1062,15 @@ class DAGScheduler
Github user markhamstra commented on a diff in the pull request:
https://github.com/apache/spark/pull/686#discussion_r14211667
--- Diff: core/src/main/scala/org/apache/spark/scheduler/DAGScheduler.scala
---
@@ -1062,10 +1062,15 @@ class DAGScheduler
Github user markhamstra commented on a diff in the pull request:
https://github.com/apache/spark/pull/1270#discussion_r14428640
--- Diff:
mllib/src/main/scala/org/apache/spark/mllib/evaluation/MultilabelMetrics.scala
---
@@ -0,0 +1,172 @@
+/*
+ * Licensed to the Apache
Github user markhamstra closed the pull request at:
https://github.com/apache/spark/pull/686
---
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 markhamstra opened a pull request:
https://github.com/apache/spark/pull/1360
SPARK-2425 Don't kill a still-running Application because of some
misbehaving Executors
Introduces a LOADING - RUNNING ApplicationState transition and prevents
Master from removing
Github user markhamstra commented on a diff in the pull request:
https://github.com/apache/spark/pull/993#discussion_r14845258
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/codegen/CodeGenerator.scala
---
@@ -0,0 +1,421
Github user markhamstra commented on a diff in the pull request:
https://github.com/apache/spark/pull/993#discussion_r14845309
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/codegen/CodeGenerator.scala
---
@@ -0,0 +1,421
Github user markhamstra commented on a diff in the pull request:
https://github.com/apache/spark/pull/993#discussion_r14846043
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/codegen/CodeGenerator.scala
---
@@ -0,0 +1,421
Github user markhamstra commented on a diff in the pull request:
https://github.com/apache/spark/pull/993#discussion_r14846216
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/codegen/CodeGenerator.scala
---
@@ -0,0 +1,421
Github user markhamstra commented on a diff in the pull request:
https://github.com/apache/spark/pull/993#discussion_r14847035
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/codegen/CodeGenerator.scala
---
@@ -0,0 +1,421
1 - 100 of 679 matches
Mail list logo
