[
https://issues.apache.org/jira/browse/HIVE-13517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15953928#comment-15953928
]
Xuefu Zhang commented on HIVE-13517:
------------------------------------
[~stakiar], Thanks for following up with this. I read thru the comments in the
Spark PR and wasn't surprised at the resistance there. This issue, if exists,
is very minor. Personally, I haven't met a case where thread-id is needed
either. Nevertheless, our production cluster has this option on, which was done
by the infra folks rather easily. Thus, I think we might just leave it as it is
today and can pick it up in the future when we have a strong use case. Thanks.
> Hive logs in Spark Executor and Driver should show thread-id.
> -------------------------------------------------------------
>
> Key: HIVE-13517
> URL: https://issues.apache.org/jira/browse/HIVE-13517
> Project: Hive
> Issue Type: Bug
> Components: Spark
> Affects Versions: 1.2.1, 2.0.0
> Reporter: Szehon Ho
> Assignee: Sahil Takiar
> Attachments: executor-driver-log.PNG, HIVE-13517.1.patch,
> HIVE-13517.2.patch
>
>
> In Spark, there might be more than one task running in one executor.
> Similarly, there may be more than one thread running in Driver.
> This makes debugging through the logs a nightmare. It would be great if there
> could be thread-ids in the logs.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
