You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ambari.apache.org by "Mugdha Varadkar (JIRA)" <ji...@apache.org> on 2016/12/01 07:01:58 UTC

[jira] [Commented] (AMBARI-19024) Handle Ambari upgrade changes to set hook flag if Atlas is available in cluster

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

Mugdha Varadkar commented on AMBARI-19024:
------------------------------------------

Addressing the above fix along with AMBARI-19007.

> Handle Ambari upgrade changes to set hook flag if Atlas is available in cluster
> -------------------------------------------------------------------------------
>
>                 Key: AMBARI-19024
>                 URL: https://issues.apache.org/jira/browse/AMBARI-19024
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>            Reporter: Mugdha Varadkar
>            Assignee: Mugdha Varadkar
>            Priority: Critical
>             Fix For: 3.0.0, 2.5.0
>
>
> As a part of changes done in AMBARI-19007, need to handle Ambari upgrade scenario which will update the hook flag if ATLAS and hook supported services are present in existing cluster.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)