ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aleksandr Kovalenko (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-12160) It is not possible to change Oozie DB/Hive DB after blueprint install
Date Fri, 26 Jun 2015 10:38:04 GMT

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

Aleksandr Kovalenko commented on AMBARI-12160:
----------------------------------------------

committed to trunk and branch-2.1.0

> It is not possible to change Oozie DB/Hive DB after blueprint install
> ---------------------------------------------------------------------
>
>                 Key: AMBARI-12160
>                 URL: https://issues.apache.org/jira/browse/AMBARI-12160
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-web
>    Affects Versions: 2.1.0
>            Reporter: Aleksandr Kovalenko
>            Assignee: Aleksandr Kovalenko
>            Priority: Critical
>             Fix For: 2.1.0
>
>         Attachments: AMBARI-12160.patch
>
>
> Was deployed cluster via blueprints. There is not present possibility to change Oozie
DB on Oozie configs page.



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

Mime
View raw message