hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sankar Hariappan (JIRA)" <>
Subject [jira] [Updated] (HIVE-16530) Improve execution logs for REPL commands
Date Thu, 04 May 2017 06:10:04 GMT


Sankar Hariappan updated HIVE-16530:
    Attachment: HIVE-16530.01.patch

> Improve execution logs for REPL commands
> ----------------------------------------
>                 Key: HIVE-16530
>                 URL:
>             Project: Hive
>          Issue Type: Sub-task
>          Components: repl
>    Affects Versions: 2.2.0
>            Reporter: Sankar Hariappan
>            Assignee: Sankar Hariappan
>              Labels: DR, replication
>         Attachments: Bootstrap_ReplDump_Console_Log.png, Bootstrap_ReplLoad_Console_Log.png,
HIVE-16530.01.patch, Incremental_ReplDump_Console_Log.png, Incremental_ReplLoad_Console_Log.png
> 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
> - 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

View raw message