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

Sergey Shelukhin edited comment on HIVE-16005 at 2/22/17 7:42 PM:
------------------------------------------------------------------

I the same method; I think I saw Hive use queryName + ":" + dagIndex elsewhere 
for this; why not here?
Also in constructThreadNameSuffix, why does it have to do the dance with all 
the IDs, aren't all of them appended if you just do attemptId toString?
Otherwise LGTM


was (Author: sershe):
I the same method; I think I saw Hive use queryName + ":" + dagIndex elsewhere 
for this; why not here?
Also in constructThreadNameSuffix, why does it have to do the dance with all 
the IDs, aren't all of them appended if you just do attemptId toString?

> miscellaneous small fixes to help with llap debuggability
> ---------------------------------------------------------
>
>                 Key: HIVE-16005
>                 URL: https://issues.apache.org/jira/browse/HIVE-16005
>             Project: Hive
>          Issue Type: Task
>            Reporter: Siddharth Seth
>            Assignee: Siddharth Seth
>         Attachments: HIVE-16005.01.patch
>
>
> - Include proc_<processname> in cli, beeline, metastore, hs2 process args
> - LLAP history logger - log QueryId instead of dagName (dag name is free 
> flowing text)
> - LLAP JXM ExecutorStatus - Log QueryId instead of dagName. Sort by running / 
> queued
> - Include thread name in TaskRunnerCallable so that it shows up in stack 
> traces (will cause extra output in logs)



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to