ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mugdha Varadkar (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMBARI-19024) Handle Ambari upgrade changes to set hook flag if Atlas is available in cluster
Date Mon, 05 Dec 2016 06:19:58 GMT

     [ https://issues.apache.org/jira/browse/AMBARI-19024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Mugdha Varadkar updated AMBARI-19024:
-------------------------------------
    Resolution: Fixed
        Status: Resolved  (was: Patch Available)

Fix committed to apache 
trunk: https://github.com/apache/ambari/commit/8ad494e97302d5da69224c7ce9e493d5f20797c1
branch-2.5: https://github.com/apache/ambari/commit/d2d7b07744855de692c231ca6b0b7f1fdd25d00c

> 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)

Mime
View raw message