Github user kishorvpatil commented on the issue:
https://github.com/apache/spark/pull/15009
@vanzin,
- I refactored unit tests
- Changed LAUNCHER_INTERNAL* variable access to package private
- Fixed some of the nits.
About passing sys.env, we want to capture set of sys.env variables while
launching the new SparkApp. In thread mode, the launching user code could
change the sys.env variables after launching application. For instance even
pollute env while launching another Spark app. We made a lot of code changes
to ensure this.
---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
