You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2018/06/21 15:52:00 UTC
[jira] [Commented] (AMBARI-24157) Backup External Metastore
Database Task should communicate properly with the user
[ https://issues.apache.org/jira/browse/AMBARI-24157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16519534#comment-16519534 ]
Hudson commented on AMBARI-24157:
---------------------------------
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #9502 (See [https://builds.apache.org/job/Ambari-trunk-Commit/9502/])
AMBARI-24157 Backup External Metastore Database Task should communicate (mgergely: [https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=fa1542dd7f703bace1b3642f500ee2b241cdd46d])
* (edit) ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/scripts/pre_upgrade.py
> Backup External Metastore Database Task should communicate properly with the user
> ---------------------------------------------------------------------------------
>
> Key: AMBARI-24157
> URL: https://issues.apache.org/jira/browse/AMBARI-24157
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.7.0
> Reporter: Miklos Gergely
> Assignee: Miklos Gergely
> Priority: Blocker
> Labels: pull-request-available
> Fix For: 2.7.0
>
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> In case of external Hive database the backup step should not fail if the db is not found, but there should be an additional step telling the user that they should check the previous step's log if the backup was successful. If it wasn't, then they should follow the instructions to do the backup manually.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)