Github user vanzin commented on the issue:
https://github.com/apache/spark/pull/17499
The bug is short on details about what exactly this helps with. Do you have
a specific situation where you found that knowing the thread helped debug
something?
I'm a little wary of adding more clutter to the default configuration. The
goal of having something like log4j is that you can customize it if you want,
and it's pretty easy to change the log4j configuration when you run Spark.
Spark-on-YARN will even ship the driver's log4j.properties to executors so you
only need to change it in one place.
So from my end I don't see a benefit in this. So far we've done a pretty
good job debugging things with the existing configs, and you can always
customize things when needed.
---
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]
