[ https://issues.apache.org/jira/browse/HIVE-13517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15941478#comment-15941478 ]
Sahil Takiar commented on HIVE-13517: ------------------------------------- Changing the {{log4j.properties}} file in the Spark installation is definitely a better solution to the thread-id issue. So perhaps we should change the goal of this JIRA to "Allow custom log4j.properties file for Hive-on-Spark Driver and Executor". Sound good? > 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)