Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/237#issuecomment-39659222
I tested this in maven and sbt builds. Seemed to work for me!
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as we
Github user shivaram commented on a diff in the pull request:
https://github.com/apache/spark/pull/237#discussion_r11324595
--- Diff: bin/compute-classpath.sh ---
@@ -59,7 +45,7 @@ if [ -f "$ASSEMBLY_DIR"/spark-assembly*hadoop*-deps.jar
]; then
CLASSPATH="$CLASSPATH:$FWDIR/
Github user aarondav commented on a diff in the pull request:
https://github.com/apache/spark/pull/237#discussion_r11324565
--- Diff: bin/compute-classpath.sh ---
@@ -59,7 +45,7 @@ if [ -f "$ASSEMBLY_DIR"/spark-assembly*hadoop*-deps.jar
]; then
CLASSPATH="$CLASSPATH:$FWDIR/
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/335
---
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 enabl
Github user pwendell commented on a diff in the pull request:
https://github.com/apache/spark/pull/237#discussion_r11324292
--- Diff: bin/compute-classpath.sh ---
@@ -71,6 +57,23 @@ else
CLASSPATH="$CLASSPATH:$ASSEMBLY_JAR"
fi
+# When Hive support is needed, Da
Github user pwendell commented on a diff in the pull request:
https://github.com/apache/spark/pull/237#discussion_r11324287
--- Diff: bin/compute-classpath.sh ---
@@ -59,7 +45,7 @@ if [ -f "$ASSEMBLY_DIR"/spark-assembly*hadoop*-deps.jar
]; then
CLASSPATH="$CLASSPATH:$FWDIR/
Github user pwendell commented on a diff in the pull request:
https://github.com/apache/spark/pull/237#discussion_r11324290
--- Diff: bin/compute-classpath.sh ---
@@ -71,6 +57,23 @@ else
CLASSPATH="$CLASSPATH:$ASSEMBLY_JAR"
fi
+# When Hive support is needed, Da
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/156#issuecomment-39657291
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/335#issuecomment-39657293
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/13814/
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/335#issuecomment-39657290
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/156#issuecomment-39657292
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/13815/
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/335#issuecomment-39656875
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/335#issuecomment-39656876
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/13813/
---
If your project
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/334
---
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 enabl
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/334#issuecomment-39656490
Thanks @srowen. I merged 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 ha
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/332#issuecomment-39656418
My thought is - if it's only a matter of saving us from having to write 10
`if` statements (which I don't think have changed or been modified in several
years), it might
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/332#issuecomment-39656388
Ah I see. If that's the case, how does this differ from the checks we
already do inside of Spark's normal logging?
https://github.com/apache/spark/blob/master/co
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/156#issuecomment-39656279
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-39656284
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 the pull request:
https://github.com/apache/spark/pull/156#issuecomment-39656235
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/182#issuecomment-39656168
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/182#issuecomment-39656169
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/13812/
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/335#issuecomment-39656158
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/335#issuecomment-39656157
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/335#issuecomment-39656091
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/335#issuecomment-39656088
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 opened a pull request:
https://github.com/apache/spark/pull/335
SPARK-1421. Make MLlib work on Python 2.6
The reason it wasn't working was passing a bytearray to stream.write(),
which is not supported in Python 2.6 but is in 2.7. (This array came from NumPy
when
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/237#issuecomment-39655971
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/237#issuecomment-39655972
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/13811/
---
If your project
Github user mateiz commented on the pull request:
https://github.com/apache/spark/pull/329#issuecomment-39655957
We should allow the empty partitions, this was intentional behavior. It's
used quite a bit in our unit tests for example. Users who want fewer partitions
can always check t
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/295#issuecomment-39655883
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-39655885
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/13808/
---
If your project is set up for it, you can r
Github user aarondav commented on a diff in the pull request:
https://github.com/apache/spark/pull/299#discussion_r11324035
--- Diff: bin/run-example ---
@@ -75,7 +75,6 @@ fi
# Set JAVA_OPTS to be able to load native libraries and to set heap size
JAVA_OPTS="$SPARK_J
Github user aarondav commented on the pull request:
https://github.com/apache/spark/pull/288#issuecomment-39655659
LGTM, would you mind bringing this up to date with master (looks like a
pretty trivial conflict).
---
If your project is set up for it, you can reply to this email and h
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/182#issuecomment-39655460
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/182#issuecomment-39655464
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 aarondav commented on the pull request:
https://github.com/apache/spark/pull/182#issuecomment-39655440
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/182#issuecomment-39655389
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/182#issuecomment-39655391
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/13810/
---
If your project is set up for it, you can r
Github user manku-timma commented on the pull request:
https://github.com/apache/spark/pull/322#issuecomment-39655348
I see that PR 334 made the java 6 change. So I reverted mine.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub a
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/237#issuecomment-39655300
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/237#issuecomment-39655298
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 the pull request:
https://github.com/apache/spark/pull/237#issuecomment-39655244
Also fixes SPARK-1309.
---
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/182#issuecomment-39655213
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/182#issuecomment-39655218
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 marmbrus commented on the pull request:
https://github.com/apache/spark/pull/332#issuecomment-39655093
Scala logging is not a new logger. This is just a set of macro functions
that call sfl4j, wrapping the logging calls in checks to see if they are
enabled. This lets you
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/334#issuecomment-39655091
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/13805/
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/334#issuecomment-39655090
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 witgo commented on the pull request:
https://github.com/apache/spark/pull/332#issuecomment-39655050
We should use unified logging interfaces and overall logging system to
migrate to scalalogging is a good idea.
---
If your project is set up for it, you can reply to this e
Github user marmbrus commented on the pull request:
https://github.com/apache/spark/pull/333#issuecomment-39655007
LGTM
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled an
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/274#issuecomment-39654682
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 f
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/274#issuecomment-39654683
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/13807/
---
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/237#issuecomment-39654658
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 f
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/237#issuecomment-39654659
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/13809/
---
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/237#issuecomment-39654636
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 fe
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/274#issuecomment-39654630
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/237#issuecomment-39654631
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/295#issuecomment-39654629
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/295#issuecomment-39654635
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/274#issuecomment-39654634
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 fe
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/274#issuecomment-39654578
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 f
Github user aarondav commented on a diff in the pull request:
https://github.com/apache/spark/pull/237#discussion_r11323799
--- Diff: project/SparkBuild.scala ---
@@ -395,8 +404,6 @@ object SparkBuild extends Build {
// assembly jar.
def hiveSettings = sharedSettings +
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/274#issuecomment-39654579
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/13806/
---
If your project is set up for it, you can r
Github user aarondav commented on the pull request:
https://github.com/apache/spark/pull/237#issuecomment-39654566
Alright, I changed up the solution by having Maven also download the
datanucleus jars into lib_managed/jars/ (unlike SBT, Maven will only download
these jars, and only wh
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/274#issuecomment-39654541
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 marmbrus commented on the pull request:
https://github.com/apache/spark/pull/295#issuecomment-39654542
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 featur
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/274#issuecomment-39654543
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 fe
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/334#issuecomment-39654514
We should probably just disable that test - it's been flaky recently.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitH
Github user pwendell commented on a diff in the pull request:
https://github.com/apache/spark/pull/267#discussion_r11323765
--- Diff: repl/src/main/scala/org/apache/spark/repl/SparkJLineReader.scala
---
@@ -78,3 +80,11 @@ class SparkJLineReader(_completion: => Completion)
extends
Github user aarondav commented on a diff in the pull request:
https://github.com/apache/spark/pull/267#discussion_r11323731
--- Diff: repl/src/main/scala/org/apache/spark/repl/SparkJLineReader.scala
---
@@ -78,3 +80,11 @@ class SparkJLineReader(_completion: => Completion)
extends
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/334#issuecomment-39654097
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/334#issuecomment-39654099
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 srowen commented on the pull request:
https://github.com/apache/spark/pull/334#issuecomment-39654021
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/334#issuecomment-39653802
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/334#issuecomment-39653804
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/13803/
---
If your project is set up for it, you can r
Github user CodingCat closed the pull request at:
https://github.com/apache/spark/pull/8
---
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 enab
Github user CodingCat commented on the pull request:
https://github.com/apache/spark/pull/8#issuecomment-39653378
closed, as Patrick said in
https://issues.apache.org/jira/browse/SPARK-1039, this won't be fixed
---
If your project is set up for it, you can reply to this email and hav
Github user kanzhang commented on the pull request:
https://github.com/apache/spark/pull/318#issuecomment-39653342
Fine with me (less work for now :-). Pushing change now.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. I
Github user mridulm commented on the pull request:
https://github.com/apache/spark/pull/148#issuecomment-39653130
Just to be clear, the current status of the patch seems to be :
a) If user specified logging config - use that.
b) If missing, use a spark config built into the jar.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/139#issuecomment-39652912
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/13802/
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/139#issuecomment-39652911
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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/308
---
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 enabl
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/302
---
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 enabl
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8#issuecomment-39652806
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 fea
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8#issuecomment-39652807
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/13804/
---
If your project is set up for it, you can rep
Github user mateiz commented on the pull request:
https://github.com/apache/spark/pull/302#issuecomment-39652679
Looks good, thanks Mridul.
---
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 thi
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8#issuecomment-39652666
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 feat
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8#issuecomment-39652655
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 f
Github user mateiz commented on the pull request:
https://github.com/apache/spark/pull/8#issuecomment-39652533
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 f
Github user pwendell commented on a diff in the pull request:
https://github.com/apache/spark/pull/274#discussion_r11323561
--- Diff: core/src/main/scala/org/apache/spark/rdd/EmptyRDD.scala ---
@@ -24,7 +24,7 @@ import org.apache.spark.{Partition, SparkContext,
TaskContext}
/*
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/274#discussion_r11323558
--- Diff:
core/src/main/scala/org/apache/spark/rdd/PartitionPruningRDD.scala ---
@@ -21,7 +21,8 @@ import scala.reflect.ClassTag
import org.apache.spar
Github user pwendell commented on a diff in the pull request:
https://github.com/apache/spark/pull/274#discussion_r11323553
--- Diff: core/src/main/scala/org/apache/spark/util/FileLogger.scala ---
@@ -36,7 +36,7 @@ import org.apache.spark.io.CompressionCodec
* @param compress
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/334#issuecomment-39652430
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/334#issuecomment-39652434
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 the pull request:
https://github.com/apache/spark/pull/308#issuecomment-39652413
Alright, going to merge this.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have
GitHub user srowen opened a pull request:
https://github.com/apache/spark/pull/334
Fix for PR #195 for Java 6
Use Java 6's recommended equivalent of Java 7's Logger.getGlobal() to
retain Java 6 compatibility. See PR #195
You can merge this pull request into a Git repository by runn
Github user pwendell commented on a diff in the pull request:
https://github.com/apache/spark/pull/274#discussion_r11323549
--- Diff:
core/src/main/scala/org/apache/spark/rdd/PartitionPruningRDD.scala ---
@@ -21,7 +21,8 @@ import scala.reflect.ClassTag
import org.apache.
Github user mateiz commented on the pull request:
https://github.com/apache/spark/pull/16#issuecomment-39652322
@holdenk this would also be good for 1.0 if you have a chance to fix it
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHu
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/332#issuecomment-39652335
/cc @marumbrus - do you have strong attachments to scala logging? For the
short term I do agree consolidating on Spark's existing logging would be nice.
In particular, do
Github user mateiz commented on a diff in the pull request:
https://github.com/apache/spark/pull/16#discussion_r11323529
--- Diff:
extras/java8-tests/src/test/java/org/apache/spark/Java8APISuite.java ---
@@ -246,6 +246,24 @@ public void mapPartitions() {
}
@Test
1 - 100 of 167 matches
Mail list logo
