Github user phalodi closed the pull request at:
https://github.com/apache/spark/pull/15134
---
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
Github user phalodi closed the pull request at:
https://github.com/apache/spark/pull/15133
---
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
Github user phalodi commented on the issue:
https://github.com/apache/spark/pull/15134
@srowen Ok no problem i will close this PR
---
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 phalodi commented on the issue:
https://github.com/apache/spark/pull/15134
@jerryshao ok i will change it as you suggested but then i think if UUID is
not a good name then we should also change it for spark session you see below
spark session generate UUID while
Github user phalodi commented on the issue:
https://github.com/apache/spark/pull/15134
@jerryshao yeah you are right jerry for spark-submit and launcher its
works, but for many time user also have usecase to just locally using spark
like reading file with spark more fast even we run
Github user phalodi commented on the issue:
https://github.com/apache/spark/pull/15134
@sadikovi Yes it will, like if we will not define app name in SparkConf
object or spark-submit then it will generate exception , In this PR random UUID
is generated for app name if its not defining
Github user phalodi commented on the issue:
https://github.com/apache/spark/pull/15134
@jerryshao yeah if you suggest i prefix spark- in front of UUID but yeah
still when user use core part of RDD when they dont need to deal with dataset
they create SparkContext and some people also
Github user phalodi commented on the issue:
https://github.com/apache/spark/pull/15134
@jerryshao We can i think like if while creating spark context for
application in its configuration i didnt define app name and at a time of
spark-submit i also not provide app name
Github user phalodi commented on the issue:
https://github.com/apache/spark/pull/15133
Also change this one according to that now default value of app name is
(random) for session and context
 if its done can you merge it.
---
If your project is set up for it, you can
Github user phalodi commented on the issue:
https://github.com/apache/spark/pull/14104
@srowen @rxin
---
If your project is set up
GitHub user phalodi opened a pull request:
https://github.com/apache/spark/pull/14135
[Spark-16479] Add Example for asynchronous action
## What changes were proposed in this pull request?
Add Example for asynchronous action
## How was this patch tested
Github user phalodi closed the pull request at:
https://github.com/apache/spark/pull/14134
---
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
GitHub user phalodi opened a pull request:
https://github.com/apache/spark/pull/14134
[Spark-16479] Add Example for asynchronous action
## What changes were proposed in this pull request?
Add examples for asynchronous actions
## How was this patch tested
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
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
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
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 asynchr
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
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 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.
