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


Imho, I do not know if the password should be put into the default stack 
definition. The user sees the passwords as '****' not knowing its true value. 
The blueprint XML is the one who should have the default password. Other 
configs I can understand having a default value.

- Srimanth Gunturi


On April 18, 2014, 9:32 p.m., Sid Wagle wrote:
> 
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/20501/
> -----------------------------------------------------------
> 
> (Updated April 18, 2014, 9:32 p.m.)
> 
> 
> Review request for Ambari, Jaimin Jetly, John Speidel, Sumit Mohanty, and 
> Srimanth Gunturi.
> 
> 
> Bugs: AMBARI-5515
>     https://issues.apache.org/jira/browse/AMBARI-5515
> 
> 
> Repository: ambari
> 
> 
> Description
> -------
> 
>  Hive deployment via Blueprints works when the following configurations were 
> added to the blueprint.
> Several of the properties do exist in the stack definition, but most don't.
> 
> 
> Diffs
> -----
> 
>   
> ambari-server/src/main/java/org/apache/ambari/server/controller/internal/ClusterResourceProvider.java
>  18031d0 
>   
> ambari-server/src/main/resources/stacks/HDP/1.3.2/services/HIVE/configuration/global.xml
>  f3c274a 
>   
> ambari-server/src/main/resources/stacks/HDP/1.3.2/services/HIVE/configuration/hive-site.xml
>  3a6ed76 
>   
> ambari-server/src/main/resources/stacks/HDP/2.0.6/services/HIVE/configuration/global.xml
>  e164c64 
>   
> ambari-server/src/main/resources/stacks/HDP/2.0.6/services/HIVE/configuration/hive-site.xml
>  6336a70 
>   
> ambari-server/src/main/resources/stacks/HDP/2.1/services/HIVE/configuration/hive-site.xml
>  16ca4c1 
> 
> Diff: https://reviews.apache.org/r/20501/diff/
> 
> 
> Testing
> -------
> 
> 
> Thanks,
> 
> Sid Wagle
> 
>

Reply via email to