-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/45247/#review125132
-----------------------------------------------------------



How are we handling errors?  Seems like we chain a bunch of calls.  The user 
would need to see what went wrong.
Also, can we get into partial failure scenarios?

- Yusaku Sako


On March 23, 2016, 8:58 p.m., Jaimin Jetly wrote:
> 
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/45247/
> -----------------------------------------------------------
> 
> (Updated March 23, 2016, 8:58 p.m.)
> 
> 
> Review request for Ambari, Srimanth Gunturi and Yusaku Sako.
> 
> 
> Bugs: AMBARI-15539
>     https://issues.apache.org/jira/browse/AMBARI-15539
> 
> 
> Repository: ambari
> 
> 
> Description
> -------
> 
> Capacity scheduler will be changed as part of saving Hive configs related to 
> adding/deleting Hive Interactive Server. So YARN Queue has to be refreshed 
> before issuing Hive Interactive Server Start/Delete command
> 
> 
> Diffs
> -----
> 
>   ambari-web/app/mixins/main/service/configs/component_actions_by_configs.js 
> 7857411 
> 
> Diff: https://reviews.apache.org/r/45247/diff/
> 
> 
> Testing
> -------
> 
> Tested the patch on a cluster
> Verified that all ambari-web unit tests passes with the patch:
> 
> 
>   24653 tests complete (24 seconds)
>   145 tests pending
> 
> 
> Thanks,
> 
> Jaimin Jetly
> 
>

Reply via email to