Github user vanzin commented on the issue:
https://github.com/apache/spark/pull/16949
re: security, this change doesn't really change anything; all this
information is already available in the UI. Note it doesn't expose the system
env (as in environment variables), although people may still expose things
through system properties and spark configuration. There's some code to redact
sensitive info and even a config to control what gets redacted, but ultimately,
the solution to security is auth + ssl. As Spark gets more and more features,
data may start leaking through other places (e.g. SQL query plans which are
shown in the UI).
As for the change, I kinda implemented it as part of my SHS project, and I
went with a slightly different API:
https://github.com/vanzin/spark/commit/d127f154310c82801b2e43408154341bd0329afe
Mainly I broke the "JVM properties" into a separate type; I kinda prefer
that instead of "magic keys", especially when these keys contain spaces and
thus don't map well to code.
---
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
