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 ]]; then
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
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
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
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-43399341
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/810#issuecomment-43399342
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/15066/
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/799#issuecomment-43398854
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/15065/
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/799#issuecomment-43398853
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/810#issuecomment-43398671
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/809#issuecomment-43397525
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 AndreSchumacher commented on the pull request:
https://github.com/apache/spark/pull/511#issuecomment-43400641
Closing this now since it got merged. Thanks everyone.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user AndreSchumacher closed the pull request at:
https://github.com/apache/spark/pull/511
---
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
Github user mridulm commented on the pull request:
https://github.com/apache/spark/pull/808#issuecomment-43401491
Though I don't think there is any issue with this change specifically,
would be better if there is atleast someone else reviews a PR and gives a
go before
Github user aarondav commented on the pull request:
https://github.com/apache/spark/pull/810#issuecomment-43401692
Retroactive LGTM... (this was just merged in immediately to go into the
next RC).
---
If your project is set up for it, you can reply to this email and have your
reply
Github user mridulm commented on the pull request:
https://github.com/apache/spark/pull/808#issuecomment-43401687
Ah ! Great :-)
Would have been more clear if at least asfgit had indicated who committed
it in the message.
On 17-May-2014 2:22 pm, Aaron Davidson
Github user aarondav commented on the pull request:
https://github.com/apache/spark/pull/808#issuecomment-43401656
I think @pwendell actually committed this (as indicated here:
https://github.com/apache/spark/commit/a80a6a139e729ee3f81ec4f0028e084d2d9f7e82).
I think he just forgot to
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/755#issuecomment-43403660
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 kanzhang commented on the pull request:
https://github.com/apache/spark/pull/755#issuecomment-43403735
re-submit patch to change a typo in commit log (block size - batch size).
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/755#issuecomment-43403661
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/755#issuecomment-43404331
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/755#issuecomment-43404332
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/15067/
---
If your project
Github user tgravescs commented on the pull request:
https://github.com/apache/spark/pull/433#issuecomment-43404871
@berngp sorry for the delay I think everyone has been busy with the spark
1.0 release. I think this should still be fixed in spark 1.1. Lets leave this
pr as is and
Github user cloud-fan commented on the pull request:
https://github.com/apache/spark/pull/791#issuecomment-43411524
This is thread safe. `tryToPut` call `ensureFreeSpace` in a synchronized
block, so there is only one thread can run `ensureFreeSpace` at the same time,
which means each
Github user mridulm commented on the pull request:
https://github.com/apache/spark/pull/791#issuecomment-43413071
Use of dropping is not my safe
On 17-May-2014 9:42 pm, Wenchen Fan notificati...@github.com wrote:
This is thread safe. tryToPut call ensureFreeSpace in a
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/811#issuecomment-43420472
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
GitHub user witgo opened a pull request:
https://github.com/apache/spark/pull/811
Convert spark.cleaner.ttl.* to lowercase
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/witgo/spark MetadataCleanerType
Alternatively you can
Github user kanzhang commented on the pull request:
https://github.com/apache/spark/pull/760#issuecomment-43423066
@witgo unfortunately I don't see an easy alternative. If you see one, pls
let me know.
---
If your project is set up for it, you can reply to this email and have your
GitHub user nevillelyh opened a pull request:
https://github.com/apache/spark/pull/812
Neville/v1.0
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/nevillelyh/spark neville/v1.0
Alternatively you can review and apply these
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/812#issuecomment-43424156
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
Github user ajtulloch commented on the pull request:
https://github.com/apache/spark/pull/726#issuecomment-43426389
Ping?
---
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
Github user mateiz commented on the pull request:
https://github.com/apache/spark/pull/770#issuecomment-43429692
@srowen Hadoop does distribute binary artifacts that work without a
dependency download, so it might be good to let them know about this. Thanks
for taking a look at the
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/813#issuecomment-43430263
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
GitHub user douglaz opened a pull request:
https://github.com/apache/spark/pull/813
SPARK-1868: Users should be allowed to cogroup at least 4 RDDs
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/douglaz/spark more_cogroups
34 matches
Mail list logo
