Github user sahilTakiar commented on the issue:
https://github.com/apache/spark/pull/17499
Thanks for taking look everyone. The original motivation for this PR comes
[HIVE-13517](https://issues.apache.org/jira/browse/HIVE-13517). It was said to
be useful for debugging HoS applications that run on YARN. I personally can't
point to a specific example where knowing the thread-id has helped debugging
Spark applications. The HIVE JIRA mentions that the logs from different threads
get mixed, which makes it difficult to debug. The idea is that adding the
thread-id to the logs will help other Spark applications too, but if thats not
the case then I think we can close this. I've tagged some HoS experts in
SPARK-20161 to see if they can provide more details.
As Marcelo said, there is still a workaround on the Hive side for this
issue, a custom log4j.properties file can always be provided.
---
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
