You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hive.apache.org by "Vineet Garg (JIRA)" <ji...@apache.org> on 2018/06/27 18:31:03 UTC

[jira] [Updated] (HIVE-16921) ability to trace the task tree created during repl load from logs

     [ https://issues.apache.org/jira/browse/HIVE-16921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Vineet Garg updated HIVE-16921:
-------------------------------
    Fix Version/s:     (was: 3.1.0)
                   3.2.0

Deferring this to 3.2.0 since the branch for 3.1.0 has been cut off.

> ability to trace the task tree created during repl load from logs
> -----------------------------------------------------------------
>
>                 Key: HIVE-16921
>                 URL: https://issues.apache.org/jira/browse/HIVE-16921
>             Project: Hive
>          Issue Type: Sub-task
>          Components: HiveServer2
>    Affects Versions: 3.0.0
>            Reporter: anishek
>            Assignee: anishek
>            Priority: Major
>             Fix For: 3.2.0
>
>
> As part of HIVE-16896 , we will be dynamically creating the task tree as we execute the bootstrap load. To make it easier to debug and understand the replication load task tree that is created in execution phase we should have additional logging enabled by default _INFO_ to log maker statements which can be searched in the logs to determine the possible task tree that is being created. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)