[
https://issues.apache.org/jira/browse/AMBARI-16443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15281392#comment-15281392
]
Hudson commented on AMBARI-16443:
---------------------------------
FAILURE: Integrated in Ambari-trunk-Commit #4827 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/4827/])
AMBARI-16443. [Hive View] - Save Default Settings should not permit
(pallav.kul:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=931021f5627de0f8e7eca85faafdfdb98326ad20])
* contrib/views/hive/src/main/resources/ui/hive-web/app/services/settings.js
> [Hive View] - Save Default Settings should not permit empty parameter values
> ----------------------------------------------------------------------------
>
> Key: AMBARI-16443
> URL: https://issues.apache.org/jira/browse/AMBARI-16443
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
> Affects Versions: 2.2.0
> Reporter: Pallav Kulshreshtha
> Assignee: Pallav Kulshreshtha
> Fix For: 2.4.0
>
> Attachments: AMBARI-16443-2_trunk.patch, Screen Shot 2016-04-21 at
> 10.58.07 AM.png, Settings.png
>
>
> User is able to add settings with empty parameter values, and save them as
> default settings. A notification gets displayed that the Settings have been
> saved. But when the user runs any query after that - an error is thrown
> because of the invalid saved setting.
> It would be better to keep a validation while adding the settings itself.
> Either provide a default value for every setting added (wherever possible),
> or do not permit the user to leave any setting's parameter value blank.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
