[
https://issues.apache.org/jira/browse/AMBARI-13969?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15014255#comment-15014255
]
Hudson commented on AMBARI-13969:
---------------------------------
ABORTED: Integrated in Ambari-trunk-Commit #3869 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/3869/])
AMBARI-13969 Validate that hive-env.sh content is valid when Ambari is (dsen:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=7603d3ff5b4df29b81d5e320ffe6f5424cbd0c57])
*
ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog213.java
*
ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog213Test.java
> Validate that hive-env.sh content is valid when Ambari is upgraded from 2.1.0
> -> 2.1.2 -> 2.1.3
> -----------------------------------------------------------------------------------------------
>
> Key: AMBARI-13969
> URL: https://issues.apache.org/jira/browse/AMBARI-13969
> Project: Ambari
> Issue Type: Bug
> Components: ambari-upgrade
> Affects Versions: 2.1.3
> Reporter: Dmytro Sen
> Assignee: Dmytro Sen
> Fix For: 2.1.3
>
> Attachments: AMBARI-13969.patch
>
>
> do one more test and upgrade from Ambari-2.1.0 to Ambari-2.1.2 and
> Amabri-2.1.2 to Ambari-2.1.3.
> Lets invoke ambari-server upgrade twice per upgrade and ensure that
> hive-env.sh has valid content for each upgrade.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
