[
https://issues.apache.org/jira/browse/AMBARI-13937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15011542#comment-15011542
]
Hudson commented on AMBARI-13937:
---------------------------------
FAILURE: Integrated in Ambari-trunk-Commit #3861 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/3861/])
AMBARI-13937. Oozie and hive db hostname should be non-editable for new
(onechiporenko:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=7031576d252e27c268b5b873f57452350d08251c])
* ambari-web/app/views/common/controls_view.js
> Oozie and hive db hostname should be non-editable for new databases
> -------------------------------------------------------------------
>
> Key: AMBARI-13937
> URL: https://issues.apache.org/jira/browse/AMBARI-13937
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
> Affects Versions: 2.1.3
> Reporter: Oleg Nechiporenko
> Assignee: Oleg Nechiporenko
> Fix For: 2.2.0
>
> Attachments: AMBARI-13937-2.patch, AMBARI-13937.patch
>
>
> This issue surfaces for both hive and oozie.
> Although ui does not eventually let the user change the field.
> *current behavior:* database hostname field is presented as editable for new
> db type when config page is loaded. when user tries to change value, it
> converts into non-editable field
> *expected behavior:* database hostname field should be presented as
> non-editable for new db type from beginning when config page is rendered.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
