[
https://issues.apache.org/jira/browse/AMBARI-14371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15064424#comment-15064424
]
Hudson commented on AMBARI-14371:
---------------------------------
FAILURE: Integrated in Ambari-trunk-Commit #4067 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/4067/])
AMBARI-14371 No eventual config changes should not recommend extra
(babiychukandrey:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=4c3d38c6f989b72a12b0c1461ba0ffca6d66ee76])
* ambari-web/app/models/configs/objects/service_config_property.js
* ambari-web/app/utils/configs/config_initializer.js
* ambari-web/app/mixins/common/serverValidator.js
* ambari-web/app/mixins/common/configs/enhanced_configs.js
* ambari-web/app/views/common/controls_view.js
* ambari-web/test/views/common/configs/widgets/list_config_widget_view_test.js
* ambari-web/app/models/configs/objects/service_config.js
* ambari-web/app/utils/configs/config_initializer_class.js
> No eventual config changes should not recommend extra config changes
> --------------------------------------------------------------------
>
> Key: AMBARI-14371
> URL: https://issues.apache.org/jira/browse/AMBARI-14371
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
> Affects Versions: 2.2.0
> Reporter: Andrii Babiichuk
> Assignee: Andrii Babiichuk
> Fix For: 2.4.0
>
> Attachments: AMBARI-14371.patch
>
>
> This ticket proposes that if user has not made any eventual config change
> (for example "Enabled Ranger plugin for HBase" and then disabled it again)
> then ambari should not show any extra config changes.
> For this we need to keep track of explicit config changes that are being made
> by the user. If a config change at any time negates all the user config
> changes done before then UI should send configs in the data posted in
> recommendation API as received from stack (on installer/ASW wizard) or the
> last service config version (post-install).
> Please find below examples:
> First example:
> On Installer/ASW, When user lands on "Customize Services" page, ui posts data
> to recommendation API with all config values as received from stack endpoint
> After that, If user changes "Ranger plugin for HBase" to ON, ui send
> recommendation API with all config values as received from stack endpoint +
> overriden value of some config received from response of API executed in
> step-1
> User Changes "Ranger plugin for HBase" to OFF, ui should post data to
> recommendation API with all config values as received from stack endpoint (as
> done in step1). The reason being the all users previously explicitly made
> changes have been negated at this point
> Second Example:
> On Installer/ASW, When user lands on "Customize Services" page, ui posts data
> to recommendation API with all config values as received from stack endpoint
> After that, If user changes "Ranger plugin for HBase" to ON and changes some
> other property "xyz" to "v1", ui send recommendation API with all config
> values as currently set in UI (received from stack endpoint + overriden value
> of some config received from response of API executed in step-1)
> Changes "Ranger plugin for HBase" to OFF, ui should post data to
> recommendation API with all config values as set currently on UI (same
> behavior as ui displays today).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
