GitHub user pwendell opened a pull request:
https://github.com/apache/spark/pull/810
Make deprecation warning less severe
Just a small change. I think it's good not to scare people who are using
the old options.
You can merge this pull request into a Git repository by running:
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/810#issuecomment-43398666
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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/810
---
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/802
---
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/799#discussion_r12766116
--- Diff: bin/pyspark ---
@@ -25,6 +25,12 @@ export SPARK_HOME="$FWDIR"
SCALA_VERSION=2.10
+if [[ "$@" = *--help ]] || [[ "$@" = *--h ]];
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/799#issuecomment-43398339
LGTM - thanks Andrew!
---
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/799#issuecomment-43398162
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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/799
---
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/799#issuecomment-43398156
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/799#discussion_r12765913
--- Diff: bin/pyspark ---
@@ -25,6 +25,12 @@ export SPARK_HOME="$FWDIR"
SCALA_VERSION=2.10
+if [[ "$@" = *--help ]] || [[ "$@" = *--h ]];
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/809
---
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/799#issuecomment-43396764
LGTM - a few minor comments. Mind taking a quick look
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If y
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/809#issuecomment-43397526
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/15064/
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/809#issuecomment-43396873
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 kanzhang commented on the pull request:
https://github.com/apache/spark/pull/760#issuecomment-43395929
@witgo yes, the first one is wrong and that is due to the Scala bug I
referenced above (https://issues.scala-lang.org/browse/SI-8518).
---
If your project is set up for
Github user witgo commented on the pull request:
https://github.com/apache/spark/pull/760#issuecomment-43396698
@kanzhang
All told, we should fix the following code
`slices += r.take(sliceSize).asInstanceOf[Seq[T]]`.
---
If your project is set up for it, you can reply to thi
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/694#issuecomment-43396183
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/799#discussion_r12765889
--- Diff: core/src/main/scala/org/apache/spark/deploy/SparkSubmit.scala ---
@@ -303,14 +309,36 @@ object SparkSubmit {
}
/**
+ * Retu
GitHub user pwendell opened a pull request:
https://github.com/apache/spark/pull/809
Version bump of spark-ec2 scripts
This will allow us to change things in spark-ec2 related to the 1.0 release.
You can merge this pull request into a Git repository by running:
$ git pull https
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/809#issuecomment-43396879
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/694#issuecomment-43395354
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/776#issuecomment-43395958
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/802#issuecomment-43395459
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/802#issuecomment-43396258
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/15063/
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/799#issuecomment-43395353
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/802#issuecomment-43396257
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/799#issuecomment-43396184
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/799#discussion_r12765879
--- Diff: bin/spark-shell ---
@@ -28,7 +28,7 @@ esac
# Enter posix mode for bash
set -o posix
-if [[ "$@" == *--help* ]]; then
+if [[ "
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/694#issuecomment-43396185
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/15062/
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/808#issuecomment-43393840
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 andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/799#issuecomment-43395322
This is ready for merge from my side, provided that the tests pass (they
should).
---
If your project is set up for it, you can reply to this email and have your
reply
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/807#issuecomment-43393108
Can one of the admins verify this patch?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your proj
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/776#issuecomment-43395160
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 andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/802#issuecomment-43395385
This is ready to merge (after #799)
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/799#issuecomment-43396186
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/15061/
---
If your project
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/808
---
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/776#issuecomment-43395959
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/15060/
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/799#issuecomment-43393272
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/799#issuecomment-43394310
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/15058/
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/799#issuecomment-43395356
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/694#issuecomment-43395357
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/776#issuecomment-43395161
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/806#issuecomment-43391034
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 a diff in the pull request:
https://github.com/apache/spark/pull/694#discussion_r12765545
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/cluster/CoarseGrainedSchedulerBackend.scala
---
@@ -140,8 +141,29 @@ class CoarseGrainedSchedulerBacken
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/808#issuecomment-43394753
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/805#issuecomment-43390447
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/15056/
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/802#issuecomment-43395461
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/694#discussion_r12765502
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/cluster/CoarseGrainedSchedulerBackend.scala
---
@@ -140,8 +141,29 @@ class CoarseGrainedSchedulerBacke
Github user mateiz commented on the pull request:
https://github.com/apache/spark/pull/776#issuecomment-43395120
Jenkins, this is 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 th
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/808#issuecomment-43394754
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/15059/
---
If your project
GitHub user marmbrus opened a pull request:
https://github.com/apache/spark/pull/808
SPARK-1864 Look in spark conf instead of system properties when propagating
configuration to executors.
You can merge this pull request into a Git repository by running:
$ git pull https://gi
Github user witgo commented on the pull request:
https://github.com/apache/spark/pull/760#issuecomment-43394756
@kanzhang
```
scala> sc.parallelize((1D to 2D).by(0.2),4).collect
res0: Array[Double] = Array(1.0, 1.2, 1.6, 1.8)
```
```
scala> sc.parallelize((
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/808#issuecomment-43393846
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 mridulm commented on the pull request:
https://github.com/apache/spark/pull/789#issuecomment-43388853
I have elaborated in the jira, but I will repeat it again for clarity:
This is adding an api for a specific case - it assumes single serialization
type (kryoser
Github user ash211 commented on a diff in the pull request:
https://github.com/apache/spark/pull/806#discussion_r12763329
--- Diff: docs/running-on-mesos.md ---
@@ -37,11 +36,25 @@ require any special patches of Mesos.
If you already have a Mesos cluster running, you can skip t
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/799#issuecomment-43394309
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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/806
---
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/799#issuecomment-43393276
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/805#issuecomment-43390444
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/806#issuecomment-43391035
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/15057/
---
If your project
GitHub user harishreedharan opened a pull request:
https://github.com/apache/spark/pull/807
SPARK-1729. Make Flume pull data from source, rather than the current pu...
...sh model
Currently Spark uses Flume's internal Avro Protocol to ingest data from
Flume. If the executor
Github user mateiz commented on the pull request:
https://github.com/apache/spark/pull/799#issuecomment-43394087
Changes look 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 this
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/793#issuecomment-43242879
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 ash211 commented on the pull request:
https://github.com/apache/spark/pull/789#issuecomment-43388939
Alternative to adding to `SparkContext`'s API, how about an API along the
lines of:
```
Seq[Class[Any]] classes = ...
KryoRegistrator.enableKryoWithClasses(
Github user mateiz commented on the pull request:
https://github.com/apache/spark/pull/805#issuecomment-43388296
Ah, sorry, I was actually working on this in parallel:
https://github.com/apache/spark/pull/806. Mind closing this PR and commenting
on that one?
---
If your project is s
Github user mateiz commented on the pull request:
https://github.com/apache/spark/pull/806#issuecomment-43392397
Great, thanks for taking a look.
---
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 andrewor14 commented on a diff in the pull request:
https://github.com/apache/spark/pull/799#discussion_r12760990
--- Diff: python/pyspark/java_gateway.py ---
@@ -76,3 +76,30 @@ def run(self):
java_import(gateway.jvm, "scala.Tuple2")
return gatewa
Github user pwendell commented on a diff in the pull request:
https://github.com/apache/spark/pull/799#discussion_r12727045
--- Diff: bin/pyspark ---
@@ -51,14 +57,20 @@ export
PYTHONPATH=$SPARK_HOME/python/lib/py4j-0.8.1-src.zip:$PYTHONPATH
# Load the PySpark shell.py script
Github user mateiz commented on the pull request:
https://github.com/apache/spark/pull/806#issuecomment-43388350
I also changed "distribution" to "binary package" here to make it more
consistent with the wording on our website.
---
If your project is set up for it, you can reply to t
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/806#issuecomment-43389137
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/799#discussion_r12760706
--- Diff: bin/pyspark ---
@@ -52,13 +58,35 @@ export
PYTHONPATH=$SPARK_HOME/python/lib/py4j-0.8.1-src.zip:$PYTHONPATH
export OLD_PYTHONSTARTUP=$PYTHONSTART
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/769#issuecomment-43279657
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/806#issuecomment-43390446
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/15055/
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/806#issuecomment-43390445
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/806#issuecomment-43389131
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 ash211 commented on a diff in the pull request:
https://github.com/apache/spark/pull/756#discussion_r12762858
--- Diff: docs/running-on-mesos.md ---
@@ -3,19 +3,123 @@ layout: global
title: Running Spark on Mesos
---
-Spark can run on clusters managed
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/806#issuecomment-43388331
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 ash211 commented on the pull request:
https://github.com/apache/spark/pull/806#issuecomment-43388649
I was using distribution because the script that creates it is called
`make-distribution.sh`. Maybe that should be renamed. Should I file a jira to
rename that to `make-b
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/797#issuecomment-43270726
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/769#issuecomment-43303541
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/799#issuecomment-43389659
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/15054/
---
If your project
Github user ueshin closed the pull request at:
https://github.com/apache/spark/pull/790
---
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/791#issuecomment-43200993
Can one of the admins verify this patch?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your proj
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/806#issuecomment-43388326
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/805#issuecomment-43388333
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 ash211 commented on the pull request:
https://github.com/apache/spark/pull/805#issuecomment-43388573
Will follow up there, thanks
---
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 mateiz commented on a diff in the pull request:
https://github.com/apache/spark/pull/802#discussion_r12723519
--- Diff: examples/src/main/python/logistic_regression.py ---
@@ -47,12 +47,12 @@ def readPointBatch(iterator):
return [matrix]
if __name__ =
Github user ash211 commented on the pull request:
https://github.com/apache/spark/pull/806#issuecomment-43389197
+1 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 a
GitHub user andrewor14 opened a pull request:
https://github.com/apache/spark/pull/802
[SPARK-1824] Remove from Python examples
A recent PR (#552) fixed this for all Scala / Java examples. We need to do
it for python too.
Note that this blocks on #799, which makes `bin/pys
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/803#issuecomment-43299372
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/15042/
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/799#issuecomment-43286480
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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/797
---
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 andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/799#issuecomment-43367475
Great catch. Looks like `--die-on-broken-pipe` was in fact not propagated
(see commit message for more details).
---
If your project is set up for it, you can reply to
Github user chenghao-intel commented on the pull request:
https://github.com/apache/spark/pull/446#issuecomment-43287344
Thanks @rxin.
It's done, can you re-test it?
---
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 ash211 opened a pull request:
https://github.com/apache/spark/pull/805
Spark 1818
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ash211/spark SPARK-1818
Alternatively you can review and apply these changes as the pa
Github user mateiz commented on a diff in the pull request:
https://github.com/apache/spark/pull/799#discussion_r12723642
--- Diff: bin/pyspark ---
@@ -25,6 +25,12 @@ export SPARK_HOME="$FWDIR"
SCALA_VERSION=2.10
+if [[ "$@" == *--help* ]]; then
+ echo "Usa
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/795#issuecomment-43258983
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 ash211 closed the pull request at:
https://github.com/apache/spark/pull/805
---
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 mateiz commented on a diff in the pull request:
https://github.com/apache/spark/pull/799#discussion_r12759418
--- Diff: bin/pyspark ---
@@ -52,13 +58,35 @@ export
PYTHONPATH=$SPARK_HOME/python/lib/py4j-0.8.1-src.zip:$PYTHONPATH
export OLD_PYTHONSTARTUP=$PYTHONSTART
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/801#issuecomment-43285131
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
1 - 100 of 466 matches
Mail list logo
