Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14104
Merged build finished. Test 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 project does not have this feature
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14104
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/62231/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14104
**[Test build #62231 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/62231/consoleFull)**
for PR 14104 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14104
**[Test build #62231 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/62231/consoleFull)**
for PR 14104 at commit
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/14104
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 this feature
enabled and
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/14104
@phalodi no need to ping. We don't merge things immediately, especially
when non-essential. It gives more time for review.
---
If your project is set up for it, you can reply to this email and have
Github user phalodi commented on the issue:
https://github.com/apache/spark/pull/14104
@srowen Is this is correct if it is then please merge it otherwise give
comment if needed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user phalodi commented on the issue:
https://github.com/apache/spark/pull/14104
@srowen Below is final screen shot as you suggested i hope its looks good
please review it and merge it.
---
If your project is set up for
Github user phalodi commented on the issue:
https://github.com/apache/spark/pull/14104
@srowen now its perfect i think at last from table to one line but yeah you
are right it good to just mention that spark provide it and not duplicate table
of actions.
---
If your project is set
Github user phalodi commented on the issue:
https://github.com/apache/spark/pull/14104
@srowen sure i will make appropriate changes and push it again
---
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 phalodi commented on the issue:
https://github.com/apache/spark/pull/14104
@srowen so what do you think we should not add this api reference in
document?
---
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 srowen commented on the issue:
https://github.com/apache/spark/pull/14104
Although I don't think it's essential to mention this API (it's in the API
doc) it wouldn't hurt to point to it here. The mention should be accurate
though. I think it's correct to say that the
Github user phalodi commented on the issue:
https://github.com/apache/spark/pull/14104
@srowen i know its nothing major just call normal functions in future but
still naive user first time who learn scala and spark dont know what are future
and all so at least we should add reference
Github user phalodi commented on the issue:
https://github.com/apache/spark/pull/14104
@srowen @rxin Please review it and give your comments.
**
for PR 14104 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14104
Merged build finished. Test 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 project does not have this feature
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14104
**[Test build #61980 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/61980/consoleFull)**
for PR 14104 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14104
**[Test build #61980 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/61980/consoleFull)**
for PR 14104 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14104
**[Test build #61979 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/61979/consoleFull)**
for PR 14104 at commit
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/14104
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 feature
enabled and wishes
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/14104
@phalodi it's a bot, not a person.
---
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 phalodi commented on the issue:
https://github.com/apache/spark/pull/14104
@AmplabJenkins I dont know i just create the issue on JIRA and make changes
and make pull request for merge , I think it is valid pull request because in
real world all application need non
36 matches
Mail list logo
