Github user squito commented on the pull request:
https://github.com/apache/spark/pull/3168#issuecomment-62323279
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
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/3168#issuecomment-62330950
Thanks I pulled 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 have
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/3168
---
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 srowen opened a pull request:
https://github.com/apache/spark/pull/3168
SPARK-1344 [DOCS] Scala API docs for top methods
Use k in javadoc of top and takeOrdered to avoid confusion with type K in
pair RDDs. I think this resolves the discussion in SPARK-1344.
You can
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/3168#issuecomment-62253627
[Test build #23098 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/23098/consoleFull)
for PR 3168 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/3168#issuecomment-62255698
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/3168#issuecomment-62255695
[Test build #23098 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/23098/consoleFull)
for PR 3168 at commit
