[ 
https://issues.apache.org/jira/browse/HIVE-6876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13965246#comment-13965246
 ] 

Hive QA commented on HIVE-6876:
-------------------------------



{color:green}Overall{color}: +1 all checks pass

Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12639481/HIVE-6876.1.patch

{color:green}SUCCESS:{color} +1 5570 tests passed

Test results: 
http://bigtop01.cloudera.org:8080/job/PreCommit-HIVE-Build/2202/testReport
Console output: 
http://bigtop01.cloudera.org:8080/job/PreCommit-HIVE-Build/2202/console

Messages:
{noformat}
Executing org.apache.hive.ptest.execution.PrepPhase
Executing org.apache.hive.ptest.execution.ExecutionPhase
Executing org.apache.hive.ptest.execution.ReportingPhase
{noformat}

This message is automatically generated.

ATTACHMENT ID: 12639481

> Logging information should include thread id
> --------------------------------------------
>
>                 Key: HIVE-6876
>                 URL: https://issues.apache.org/jira/browse/HIVE-6876
>             Project: Hive
>          Issue Type: Improvement
>          Components: HiveServer2, Metastore
>    Affects Versions: 0.14.0
>            Reporter: Vikram Dixit K
>            Assignee: Vikram Dixit K
>            Priority: Trivial
>         Attachments: HIVE-6876.1.patch
>
>
> The multi-threaded nature of hive server and remote metastore makes it 
> difficult to debug issues without enabling thread information. It would be 
> nice to have the thread id in the logs.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to