Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/139
---
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 the pull request:
https://github.com/apache/spark/pull/139#issuecomment-41361667
Thanks Holden! I've merged this in.
---
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 holdenk commented on the pull request:
https://github.com/apache/spark/pull/139#issuecomment-41229100
@mateiz I merged master in and fixed the conflicts, let me know if there is
anything else you need on my end.
---
If your project is set up for it, you can reply to this
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/139#issuecomment-41106525
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/139#issuecomment-41106526
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/14342/
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/139#issuecomment-41103003
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/139#issuecomment-41102989
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/139#issuecomment-40781680
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/139#issuecomment-40781681
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/14222/
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/139#issuecomment-40780535
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/139#issuecomment-40780530
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 mateiz commented on the pull request:
https://github.com/apache/spark/pull/139#issuecomment-40780446
Yes, we should do it. It looks pretty good.
---
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 mateiz commented on the pull request:
https://github.com/apache/spark/pull/139#issuecomment-40780447
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 holdenk commented on the pull request:
https://github.com/apache/spark/pull/139#issuecomment-40672235
@mateiz : Do you still think we should try and get this in for 1.0 / is it
in a good state to merge?
---
If your project is set up for it, you can reply to this email and
Github user holdenk commented on the pull request:
https://github.com/apache/spark/pull/139#issuecomment-40014184
Should I still try and get this merged for 1.0?
---
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 pro
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/139#issuecomment-39814560
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/13879/
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/139#issuecomment-39814559
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/139#issuecomment-39811442
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/139#issuecomment-39811446
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/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 mateiz commented on the pull request:
https://github.com/apache/spark/pull/139#issuecomment-39652175
@holdenk found a few small bugs in this, but this would be good to include
in 1.0
---
If your project is set up for it, you can reply to this email and have your
reply app
Github user mateiz commented on a diff in the pull request:
https://github.com/apache/spark/pull/139#discussion_r11323491
--- Diff: python/pyspark/rdd.py ---
@@ -566,7 +566,32 @@ def func(iterator):
vals = self.mapPartitions(func).collect()
return reduce(op
Github user mateiz commented on a diff in the pull request:
https://github.com/apache/spark/pull/139#discussion_r11323477
--- Diff: python/pyspark/rdd.py ---
@@ -566,7 +566,32 @@ def func(iterator):
vals = self.mapPartitions(func).collect()
return reduce(op
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/139#issuecomment-39652096
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/139#issuecomment-39652093
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 mateiz commented on the pull request:
https://github.com/apache/spark/pull/139#issuecomment-39652072
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/139#issuecomment-38881890
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
28 matches
Mail list logo
