ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Oleg Nechiporenko (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-13937) Oozie and hive db hostname should be non-editable for new databases
Date Wed, 18 Nov 2015 09:48:10 GMT

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

Oleg Nechiporenko commented on AMBARI-13937:
--------------------------------------------

 10319 tests complete (14 seconds)
  115 tests pending

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

Mime
View raw message