[ https://issues.apache.org/jira/browse/HIVE-13517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15940961#comment-15940961 ]
Sahil Takiar commented on HIVE-13517: ------------------------------------- Yes, they could just write their own log4j.properties file and specify it in {{hive.spark.log4j.file}} - but I think having a log4j file with out-of-the-box support for thread-id in the logs would improve usability. > 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)