[
https://issues.apache.org/jira/browse/HIVE-16530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16009286#comment-16009286
]
ASF GitHub Bot commented on HIVE-16530:
---------------------------------------
Github user sankarh closed the pull request at:
https://github.com/apache/hive/pull/176
> Add HS2 operation logs and improve 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
> Labels: DR, replication
> Fix For: 3.0.0
>
> Attachments: Bootstrap_ReplDump_Console_Log.png,
> Bootstrap_ReplLoad_Console_Log.png, HIVE-16530.01.patch, HIVE-16530.02.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 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)
