Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/126#issuecomment-39814456
This passed tests, it appears there was an issue with the junit output
stuff on jenkins...
---
If your project is set up for it, you can reply to this email and have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/242#issuecomment-39814558
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/13878/
---
If your project is set up for it, you can
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/126#issuecomment-39814562
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/13880/
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/126#issuecomment-39814561
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/217#issuecomment-39815143
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/217#issuecomment-39815228
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/217#issuecomment-39815229
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/13881/
---
If your project is set up for it, you can
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/126#issuecomment-39816204
Looks good to me. Thanks @tdas and @andrewor14 for a ton of work on this
patch. I'll merge this.
---
If your project is set up for it, you can reply to this email and
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/126#issuecomment-39816346
Merged into 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
Github user witgo commented on the pull request:
https://github.com/apache/spark/pull/126#issuecomment-39816405
Good job, guys.
---
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 techaddict opened a pull request:
https://github.com/apache/spark/pull/356
SPARK-1428: MLlib should convert non-float64 NumPy arrays to float64
instead of complaining
You can merge this pull request into a Git repository by running:
$ git pull
GitHub user witgo opened a pull request:
https://github.com/apache/spark/pull/357
Fix:SPARK-1441 Compile Spark Core error with Hadoop 0.23.x
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/witgo/spark SPARK-1441
Alternatively
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/351#issuecomment-39817138
I don't think this merges cleanly at present - mind up-merging it? Also the
test utility has been merged into mater now so you can remove it from this PR.
---
If your
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/247#issuecomment-39817343
Looks good TD, merging 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
GitHub user hsaputra opened a pull request:
https://github.com/apache/spark/pull/358
Remove extra semicolon in import statement and unused import in
ApplicationMaster
Small nit cleanup to remove extra semicolon and unused import in Yarn's
stable ApplicationMaster (it bothers me
Github user pwendell commented on a diff in the pull request:
https://github.com/apache/spark/pull/217#discussion_r11378521
--- Diff: core/src/main/scala/org/apache/spark/TestUtils.scala ---
@@ -95,4 +109,22 @@ object TestUtils {
result.renameTo(out)
out
}
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/357#issuecomment-39817720
You're not enabling the yarn-alpha build profile here, and Hadoop 0.23.x is
what it's for. Similarity for SBT although the profile is enabled by the
SPARK_YARN env
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/358#issuecomment-39817779
bothers me too. will merge once jenkins is happy.
---
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/358#issuecomment-39817794
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 pwendell commented on a diff in the pull request:
https://github.com/apache/spark/pull/217#discussion_r11378555
--- Diff: core/src/main/scala/org/apache/spark/TestUtils.scala ---
@@ -42,6 +42,20 @@ object TestUtils {
}
/**
+ * Create a jar that
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/358#issuecomment-39817788
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 srowen commented on the pull request:
https://github.com/apache/spark/pull/358#issuecomment-39818305
Meta question - all of the unused imports can be zapped in one go with an
IDE and semicolons too. Is that worth one big PR here?
---
If your project is set up for it, you
Github user mengxr commented on the pull request:
https://github.com/apache/spark/pull/345#issuecomment-39818345
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/296#issuecomment-39818431
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 pwendell commented on a diff in the pull request:
https://github.com/apache/spark/pull/217#discussion_r11378778
--- Diff:
repl/src/main/scala/org/apache/spark/repl/ExecutorClassLoader.scala ---
@@ -26,21 +26,28 @@ import org.apache.hadoop.fs.{FileSystem, Path}
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/296#issuecomment-39818423
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/345#issuecomment-39818419
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/345#issuecomment-39818430
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 mengxr commented on the pull request:
https://github.com/apache/spark/pull/296#issuecomment-39818904
@mateiz , I added `computeSVD` and `computeGramianMatrix` to
`IndexedRowMatrix`. Covariance and PCA computation are affected by empty rows.
Maybe we can assume
Github user pwendell commented on a diff in the pull request:
https://github.com/apache/spark/pull/217#discussion_r11378988
--- Diff:
repl/src/main/scala/org/apache/spark/repl/ExecutorClassLoader.scala ---
@@ -26,21 +26,28 @@ import org.apache.hadoop.fs.{FileSystem, Path}
Github user hsaputra commented on the pull request:
https://github.com/apache/spark/pull/358#issuecomment-39819023
@srowen there has been PRs to remove unnecessary semicolons and imports
before and I believe we had remove most of them.
Probably the best way to have some kind
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/16#issuecomment-39819091
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 this
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/16#issuecomment-39819097
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 the pull request:
https://github.com/apache/spark/pull/325#issuecomment-39819593
@AndreSchumacher
You're right,the code has been modified.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/126
---
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/358#issuecomment-39820120
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/13882/
---
If your project is set up for it, you can
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/358#issuecomment-39820119
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/298#issuecomment-39820261
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/217#issuecomment-39820263
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/217#issuecomment-39820273
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/298#issuecomment-39820270
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/351#issuecomment-39820259
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/351#issuecomment-39820268
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/217#issuecomment-39820353
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/13888/
---
If your project is set up for it, you can
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/217#issuecomment-39820352
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/345#issuecomment-39821086
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/345#issuecomment-39821087
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/13883/
---
If your project
Github user pwendell commented on a diff in the pull request:
https://github.com/apache/spark/pull/242#discussion_r11379907
--- Diff: core/src/main/scala/org/apache/spark/rdd/PairRDDFunctions.scala
---
@@ -298,7 +298,8 @@ class PairRDDFunctions[K: ClassTag, V: ClassTag](self:
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/217#issuecomment-39821357
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/217#issuecomment-39821371
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 kayousterhout commented on the pull request:
https://github.com/apache/spark/pull/305#issuecomment-39821467
I've merged this into 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
Github user haosdent commented on the pull request:
https://github.com/apache/spark/pull/194#issuecomment-39821743
@pwendell @marmbrus Could you help me review this pull request again? Thank
you in advance.
---
If your project is set up for it, you can reply to this email and have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/16#issuecomment-39822160
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/296#issuecomment-39822162
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/13884/
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/16#issuecomment-39822161
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/13885/
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/296#issuecomment-39822159
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 mengxr commented on the pull request:
https://github.com/apache/spark/pull/268#issuecomment-39822204
@yinxusen Yes, let's wait until #296 gets merged. Thanks for being patient!
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user pwendell commented on a diff in the pull request:
https://github.com/apache/spark/pull/242#discussion_r11380250
--- Diff: core/src/main/scala/org/apache/spark/rdd/PairRDDFunctions.scala
---
@@ -328,9 +330,10 @@ class PairRDDFunctions[K: ClassTag, V: ClassTag](self:
Github user pwendell commented on a diff in the pull request:
https://github.com/apache/spark/pull/242#discussion_r11380312
--- Diff: core/src/test/java/org/apache/spark/JavaAPISuite.java ---
@@ -78,6 +79,38 @@ public int compare(Integer a, Integer b) {
}
}
Github user mengxr commented on the pull request:
https://github.com/apache/spark/pull/268#issuecomment-39822477
Btw, can we use sample variance instead of population variance?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user pwendell commented on a diff in the pull request:
https://github.com/apache/spark/pull/242#discussion_r11380438
--- Diff:
extras/java8-tests/src/test/java/org/apache/spark/Java8APISuite.java ---
@@ -60,6 +60,16 @@ public void tearDown() {
Github user pwendell commented on a diff in the pull request:
https://github.com/apache/spark/pull/242#discussion_r11380428
--- Diff:
examples/src/main/java/org/apache/spark/examples/JavaPageRank.java ---
@@ -86,12 +87,18 @@ public Double call(ListString rs) {
for (int
Github user yinxusen commented on the pull request:
https://github.com/apache/spark/pull/268#issuecomment-39822920
@mengxr Yep, I have substituted the population variance with sample
variance. See line 97. in VectorRDDStatistics.
---
If your project is set up for it, you can reply
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/351#issuecomment-39823030
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/13886/
---
If your project is set up for it, you can
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/351#issuecomment-39823028
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 this
Github user BlackNiuza commented on the pull request:
https://github.com/apache/spark/pull/194#issuecomment-39823084
This PR looks good to me.
---
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 pwendell commented on the pull request:
https://github.com/apache/spark/pull/355#issuecomment-39823493
Are the api's backwards compatible in mesos? Or could this cause
incompatibilities for certain users?
---
If your project is set up for it, you can reply to this email
GitHub user ahirreddy opened a pull request:
https://github.com/apache/spark/pull/359
Pysql
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ahirreddy/spark pysql
Alternatively you can review and apply these changes as the patch
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/359#issuecomment-39824109
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/359#issuecomment-39824095
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 haosdent commented on the pull request:
https://github.com/apache/spark/pull/194#issuecomment-39824171
OK, I see. Thank you for your reply. :-) @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
Github user ahirreddy closed the pull request at:
https://github.com/apache/spark/pull/359
---
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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/305
---
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/359#issuecomment-39824273
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/359#issuecomment-39824274
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/13890/
---
If your project is set up for it, you can
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/217#issuecomment-39825018
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/298#issuecomment-39825019
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/13887/
---
If your project is set up for it, you can
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/217#issuecomment-39825020
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/13889/
---
If your project is set up for it, you can
Github user pelick commented on the pull request:
https://github.com/apache/spark/pull/355#issuecomment-39825191
List several main improvements that mean something to spark ?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user yinxusen commented on a diff in the pull request:
https://github.com/apache/spark/pull/268#discussion_r11382104
--- Diff:
mllib/src/main/scala/org/apache/spark/mllib/rdd/VectorRDDFunctions.scala ---
@@ -0,0 +1,208 @@
+/*
+ * Licensed to the Apache Software
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/242#issuecomment-39841083
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 tgravescs commented on a diff in the pull request:
https://github.com/apache/spark/pull/204#discussion_r11388641
--- Diff: bin/spark-class ---
@@ -47,9 +47,9 @@ DEFAULT_MEM=${SPARK_MEM:-512m}
SPARK_DAEMON_JAVA_OPTS=$SPARK_DAEMON_JAVA_OPTS
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/242#issuecomment-39845685
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/13891/
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/242#issuecomment-39845684
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 tgravescs commented on a diff in the pull request:
https://github.com/apache/spark/pull/204#discussion_r11389162
--- Diff:
core/src/main/scala/org/apache/spark/deploy/history/HistoryServer.scala ---
@@ -0,0 +1,265 @@
+/*
+ * Licensed to the Apache Software
Github user tgravescs commented on a diff in the pull request:
https://github.com/apache/spark/pull/204#discussion_r11389264
--- Diff:
core/src/main/scala/org/apache/spark/deploy/history/HistoryServer.scala ---
@@ -0,0 +1,265 @@
+/*
+ * Licensed to the Apache Software
Github user tgravescs commented on the pull request:
https://github.com/apache/spark/pull/204#issuecomment-39849170
I realized I'm unfortunately still hitting SPARK-1407 also. I'll look at
the issue running on secure hdfs this morning. I haven't reviewed the changes
to the
Github user tgravescs commented on a diff in the pull request:
https://github.com/apache/spark/pull/344#discussion_r11390149
--- Diff: core/src/main/scala/org/apache/spark/ui/SparkUI.scala ---
@@ -112,6 +112,11 @@ private[spark] class SparkUI(
logInfo(Stopped Spark Web UI
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/344#issuecomment-39850494
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/344#issuecomment-39850477
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 hsaputra commented on the pull request:
https://github.com/apache/spark/pull/358#issuecomment-39851403
Seems like Jenkins had build error related to some PySpark file parsing.
Can we try it again?
---
If your project is set up for it, you can reply to this email and
Github user tgravescs commented on the pull request:
https://github.com/apache/spark/pull/204#issuecomment-39853553
For some reason I seem to have to refresh my browser twice in order to pick
up new applications. Have you seen this or is it just something funky with my
browser?
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/344#issuecomment-39855170
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 techaddict commented on the pull request:
https://github.com/apache/spark/pull/356#issuecomment-39857157
@mengxr ok i'll try adding some test's
---
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 techaddict commented on the pull request:
https://github.com/apache/spark/pull/355#issuecomment-39857208
@pwendell yupp it is fully compatible although i'm checking every single
line :+1:
---
If your project is set up for it, you can reply to this email and have your
GitHub user AndreSchumacher opened a pull request:
https://github.com/apache/spark/pull/360
SPARK-1293 [SQL] WIP Parquet support for nested types
It should be possible to import and export data stored in Parquet's
columnar format that contains nested types. For example:
```java
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/360#issuecomment-39861375
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/360#issuecomment-39861391
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 AndreSchumacher commented on the pull request:
https://github.com/apache/spark/pull/360#issuecomment-39861625
@marmbrus I had to do some changes to both the attribute resolution and the
SQLParser. Would be great if you could have a look. I think it would be
actually much
Github user tgravescs commented on a diff in the pull request:
https://github.com/apache/spark/pull/204#discussion_r11394897
--- Diff:
core/src/main/scala/org/apache/spark/deploy/history/HistoryServer.scala ---
@@ -0,0 +1,265 @@
+/*
+ * Licensed to the Apache Software
1 - 100 of 334 matches
Mail list logo
