Github user rxin commented on the issue:
https://github.com/apache/spark/pull/17499
Great - please close this. Thanks!
---
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
Github user sahilTakiar commented on the issue:
https://github.com/apache/spark/pull/17499
Sounds like we agree that if this should be done, it should be done in
Hive. We have an open JIRA (HIVE-13517) to address this.
If there are no other comments, I'll close this PR and
Github user rxin commented on the issue:
https://github.com/apache/spark/pull/17499
Maybe Hive can do it in Hive.
---
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
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
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
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/17499
CC maybe @vanzin or @squito who might comment on whether this is disruptive
for apps that parse the logs?
---
If your project is set up for it, you can reply to this email and have your
reply
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17499
Can one of the admins verify this patch?
---
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
Github user sahilTakiar commented on the issue:
https://github.com/apache/spark/pull/17499
I'm not sure how the community feels about adding this to the default log4j
files, so posting this as a reference for now. Some more details are in the
JIRA, but this can improve debugabbility,
