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

Hudson commented on AMBARI-25209:
---------------------------------

SUCCESS: Integrated in Jenkins build Ambari-branch-2.7 #573 (See 
[https://builds.apache.org/job/Ambari-branch-2.7/573/])
AMBARI-25209 : Bulk Operation Refresh Configs for selected hosts (#2901) 
(asnaik: 
[https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=6885de49d69ba1cb6e9f85b5c75019db645d8d9c])
* (edit) ambari-web/app/controllers/main/host/bulk_operations_controller.js
* (edit) ambari-web/app/views/main/host/hosts_table_menu_view.js
* (edit) ambari-web/app/messages.js


> Bulk Operation Refresh Configs for selected hosts
> -------------------------------------------------
>
>                 Key: AMBARI-25209
>                 URL: https://issues.apache.org/jira/browse/AMBARI-25209
>             Project: Ambari
>          Issue Type: Improvement
>          Components: ambari-server, ambari-web
>    Affects Versions: trunk, 2.7.4
>            Reporter: Viraj Jasani
>            Assignee: Viraj Jasani
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: trunk, 2.7.4
>
>          Time Spent: 7h
>  Remaining Estimate: 0h
>
> There are multiple requirements of performing Refresh Configs after some 
> config update or as a recovery from failures. This operation should be 
> provided as a bulk operation on selective hosts so that all client components 
> can be refreshed on all selected hosts.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to