[
https://issues.apache.org/jira/browse/HIVE-13517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15941462#comment-15941462
]
Sahil Takiar commented on HIVE-13517:
-------------------------------------
[~xuefuz] I'll open a ticket on the Spark side for adding the thread id to the
default {{log4j.properties}} file. I think the patch is still useful for users
who want a workaround until the Spark support is added. Also, allowing for a
custom {{log4j.properties}} allows users to fully configure the log format,
control log levels, etc; and different users can use different
{{log4j.properties}} files.
> 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)
