hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hive QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HIVE-16530) Improve execution logs for REPL commands
Date Thu, 04 May 2017 07:52:04 GMT

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

Hive QA commented on HIVE-16530:
--------------------------------



Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12866340/HIVE-16530.01.patch

{color:red}ERROR:{color} -1 due to no test(s) being added or modified.

{color:green}SUCCESS:{color} +1 due to 10649 tests passed

Test results: https://builds.apache.org/job/PreCommit-HIVE-Build/5040/testReport
Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/5040/console
Test logs: http://104.198.109.242/logs/PreCommit-HIVE-Build-5040/

Messages:
{noformat}
Executing org.apache.hive.ptest.execution.TestCheckPhase
Executing org.apache.hive.ptest.execution.PrepPhase
Executing org.apache.hive.ptest.execution.ExecutionPhase
Executing org.apache.hive.ptest.execution.ReportingPhase
{noformat}

This message is automatically generated.

ATTACHMENT ID: 12866340 - PreCommit-HIVE-Build

> 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
>              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
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