Github user vanzin commented on the pull request:
https://github.com/apache/spark/pull/4220#issuecomment-71923968
Kinda diverging into off-topic territory, but...
> It seems like having multiple apps futzing w/ the system properties at
the same time is bound to create problems.
Yeah, this is one of those things that keep ringing in my head all the
time. I think we should have a plan to have some Spark-specific entry point
(e.g. `main(args: Array[String], conf: SparkConf)`) that is used in lieu of the
usual `main` if it's found. That could prevent having `SparkSubmit` and tests
mess with system properties at all.
But that's for another PR, this one looks good as it is (perhaps after
fixing the offending test).
---
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 [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
