[
https://issues.apache.org/jira/browse/HIVE-19880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16512819#comment-16512819
]
Hive QA commented on HIVE-19880:
--------------------------------
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:red}-1{color} | {color:red} patch {color} | {color:red} 0m 13s{color}
| {color:red}
/data/hiveptest/logs/PreCommit-HIVE-Build-11785/patches/PreCommit-HIVE-Build-11785.patch
does not apply to master. Rebase required? Wrong Branch? See
http://cwiki.apache.org/confluence/display/Hive/HowToContribute for help.
{color} |
\\
\\
|| Subsystem || Report/Notes ||
| Console output |
http://104.198.109.242/logs//PreCommit-HIVE-Build-11785/yetus.txt |
| Powered by | Apache Yetus http://yetus.apache.org |
This message was automatically generated.
> Repl Load to return recoverable vs non-recoverable error codes
> --------------------------------------------------------------
>
> Key: HIVE-19880
> URL: https://issues.apache.org/jira/browse/HIVE-19880
> 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
>
>
> 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
(v7.6.3#76005)
