You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hive.apache.org by "Sankar Hariappan (JIRA)" <ji...@apache.org> on 2017/04/25 17:31:04 UTC
[jira] [Created] (HIVE-16530) Improve execution logs for REPL
commands
Sankar Hariappan created HIVE-16530:
---------------------------------------
Summary: 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 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)