[
https://issues.apache.org/jira/browse/HIVE-13517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15939618#comment-15939618
]
liyunzhang_intel commented on HIVE-13517:
-----------------------------------------
[~stakiar]: LGTM, but what i am confused
{quote}
In a future patch, we could add a better default log4j properties file, which
has the thread-id.
{quote}
Based on HIVE-13517.2.patch, if users want a specified pattern(like contains
thread-id) in log4j.properties, they can write the pattern in
{{hive.spark.log4j.file}}, why need add a better default log4j.properties later?
> 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)
