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
e
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
[`845a123`](https://github.com/apache/spark/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
[`845a123`](https://github.com/apache/spark/commit/8
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 wishe
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.
![screenshot from 2016-07-11
17-45-24](https://cloud.githubusercontent.com/assets/8075390
Github user phalodi commented on the issue:
https://github.com/apache/spark/pull/14104
@srowen I put back-tick-quote for foreach, foreachAsync and FutureAction.
---
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 phalodi commented on the issue:
https://github.com/apache/spark/pull/14104
@srowen Thanks man i know i am not giving correct language but my intention
is also same i hope its final commit :) if its done can you merge it.
---
If your project is set up for it, you can reply
Github user phalodi commented on the issue:
https://github.com/apache/spark/pull/14104
@srowen @rxin
![screenshot from 2016-07-11
16-51-53](https://cloud.githubusercontent.com/assets/8075390/16729090/e860ff50-4787-11e6-915e-7e39da6558e3.png)
---
If your project is set up for it
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 u
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 n
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 you
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 Spark
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.
![screenshot from 2016-07-11
01-08-21](https://cloud.githubusercontent.com/assets/8075390/16715663/1305e0f6-4704-11e6-90e0-15f76a7bb1f8
Github user phalodi commented on the issue:
https://github.com/apache/spark/pull/14104
@srowen i make changes as you suggest i remove the table and add a single
below actions table and also change statement to be more clear about non
blocking.
---
If your project is set up for it, y
Github user phalodi commented on the issue:
https://github.com/apache/spark/pull/14104
@srowen ok no problem so what you suggest should i remove the table and
just add the line below the actions table and give link to scala and java docs?
And the line "Spark provide asynchronous actio
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/14104
I fixed my comment above, sorry. They _do_ block the calling thread, but
actions triggered in different threads on one RDD do not block each other. The
first sentence isn't correct. My suggestion is
Github user phalodi commented on the issue:
https://github.com/apache/spark/pull/14104
@srowen yeah i agree with you its same like non async actions but yeah we
should list it because its more useful in real life application when single
application running multiple jobs of different u
Github user phalodi commented on the issue:
https://github.com/apache/spark/pull/14104
@srowen yeah you are right its not blocking calling thread but they execute
sequentially right but in async action its return future so its running on
different threads soo not run sequentially soo
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/14104
Mostly this just duplicates the non-async documentation. I think it's worth
mentioning the existence of the async methods with a pointer to the API docs,
but, I don't think this table adds value.
-
Github user phalodi commented on the issue:
https://github.com/apache/spark/pull/14104
@rxin Below are screen shot of Asynchronous Actions inside actions and
screen shot of index of programming guide.
![screenshot from 2016-07-09
14-20-54](https://cloud.githubusercontent.com
Github user rxin commented on the issue:
https://github.com/apache/spark/pull/14104
Can you paste a screenshot of the doc?
---
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
enable
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
e
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/61979/
Test PASSed.
---
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/61980/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14104
**[Test build #61979 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/61979/consoleFull)**
for PR 14104 at commit
[`aba737f`](https://github.com/apache/spark/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
e
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
[`aba737f`](https://github.com/apache/spark/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
[`aba737f`](https://github.com/apache/spark/commit/a
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
[`aba737f`](https://github.com/apache/spark/commit/a
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 a
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 blocking
36 matches
Mail list logo