hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hive QA (JIRA)" <>
Subject [jira] [Commented] (HIVE-19880) Repl Load to return recoverable vs non-recoverable error codes
Date Sun, 17 Jun 2018 13:32:00 GMT


Hive QA commented on HIVE-19880:

Here are the results of testing the latest attachment:

{color:green}SUCCESS:{color} +1 due to 2 test(s) being added or modified.

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

Test results:
Console output:
Test logs:

Executing org.apache.hive.ptest.execution.TestCheckPhase
Executing org.apache.hive.ptest.execution.PrepPhase
Executing org.apache.hive.ptest.execution.YetusPhase
Executing org.apache.hive.ptest.execution.ExecutionPhase
Executing org.apache.hive.ptest.execution.ReportingPhase

This message is automatically generated.

ATTACHMENT ID: 12927944 - PreCommit-HIVE-Build

> Repl Load to return recoverable vs non-recoverable error codes
> --------------------------------------------------------------
>                 Key: HIVE-19880
>                 URL:
>             Project: Hive
>          Issue Type: Task
>          Components: repl
>    Affects Versions: 3.1.0, 4.0.0
>            Reporter: mahesh kumar behera
>            Assignee: mahesh kumar behera
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 3.1.0, 4.0.0
>         Attachments: HIVE-19880.01.patch, HIVE-19880.04.patch
> To enable bootstrap of large databases, application has to have the ability to keep
retrying the bootstrap load till it encounters a fatal error. The ability to identify if an
error is fatal or not will be decided by hive and communication of the same will happen to
application via error codes.
> So there should be different error codes for recoverable vs non-recoverable failures
which should be propagated to application as part of running the repl load command.

This message was sent by Atlassian JIRA

View raw message