[
https://issues.apache.org/jira/browse/AMBARI-12160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14602786#comment-14602786
]
Hudson commented on AMBARI-12160:
---------------------------------
FAILURE: Integrated in Ambari-trunk-Commit #3006 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/3006/])
AMBARI-12160. It is not possible to change Oozie DB/Hive DB after blueprint
install (akovalenko) (akovalenko:
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=65b59e51fcd5e941fe1e23601d104fc41828a504)
* ambari-web/app/utils/config.js
> 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)
