hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HIVE-16530) Improve execution logs for REPL commands
Date Wed, 03 May 2017 21:58:04 GMT

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

ASF GitHub Bot commented on HIVE-16530:
---------------------------------------

GitHub user sankarh opened a pull request:

    https://github.com/apache/hive/pull/176

    HIVE-16530: Improve execution logs for REPL commands

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/sankarh/hive HIVE-16530

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/hive/pull/176.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #176
    
----
commit d9a5e0aaf317cfdd60d1f2b62840e3f03d0fd1ac
Author: Sankar Hariappan <mailtosankarh@gmail.com>
Date:   2017-05-03T21:54:41Z

    HIVE-16530: Improve execution logs for REPL commands

----


> Improve execution logs for REPL commands
> ----------------------------------------
>
>                 Key: HIVE-16530
>                 URL: https://issues.apache.org/jira/browse/HIVE-16530
>             Project: Hive
>          Issue Type: Sub-task
>          Components: repl
>    Affects Versions: 2.2.0
>            Reporter: Sankar Hariappan
>            Assignee: Sankar Hariappan
>
> This is the log format that is being proposed for Hive Repl query logs
> For bootstrap case:
> Hive will log a message for each object as it is being bootstrapped and it will be in
the following sequence
> - Tables first (views are tables for this purpose) at time including partitions (depth
first), followed by functions, constraints 
> - The ordering is based on the ordering of listStatus API of HDFS
> - For each object, a message at the beginning of the replication will be logged
> - Every partition bootstrapped will be followed by a message saying the number of partitions
bootstrapped so far (for the table) and the partition name
> - And a message at the end of bootstrap of an object
> Incremental case:
> - We will have DB Name, event id and event type  will be part of the log header (for
debugging/troubleshooting)
> - We will have information of current event ID and total number of events to replicate
for every event replicated.



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

Mime
View raw message