> On Квітень 21, 2017, 11:56 до полудня, Sandor Magyari wrote:
> > ambari-server/src/main/java/org/apache/ambari/server/topology/AmbariContext.java
> > Lines 430 (patched)
> > <https://reviews.apache.org/r/58568/diff/1/?file=1695482#file1695482line430>
> >
> >     But in case we fix updatedConfigTypes in general, to filter out config 
> > types recommended by SA not related to any service in BP, then I think we 
> > don't need to treat core-site here. May be we can hadnle the null in 
> > general, logging a warn message.
> 
> Sandor Magyari wrote:
>     Ok, just reproduced the issue and it seems BlueprintConfigProcessor 
> configures the proxy users regradeless there's HDFS or not, so we had to fix 
> it there, until that we can have this check here.

Please take a look at my and Sumits reply here 
https://hortonworks.jira.com/browse/BUG-76895?focusedCommentId=574902&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-574902


- Vitalyi


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


On Квітень 20, 2017, 2:19 після полудня, Vitalyi Brodetskyi wrote:
> 
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/58568/
> -----------------------------------------------------------
> 
> (Updated Квітень 20, 2017, 2:19 після полудня)
> 
> 
> Review request for Ambari, Madhuvanthi Radhakrishnan, Sumit Mohanty, and 
> Sebastian Toader.
> 
> 
> Bugs: AMBARI-20802
>     https://issues.apache.org/jira/browse/AMBARI-20802
> 
> 
> Repository: ambari
> 
> 
> Description
> -------
> 
> When a minimal Blueprint install was attempted in that issue, some failures 
> occurred during the Blueprint deployment.
> After some investigation, we determined that the Blueprints processor was 
> throwing a NullPointerException, due to some configuration types being 
> considered "updated", even though those configuration types are not included 
> in the "desired configuration" for the cluster, since the services associated 
> with those configuration types are not deployed in this current cluster.
> 
> 
> Diffs
> -----
> 
>   
> ambari-server/src/main/java/org/apache/ambari/server/topology/AmbariContext.java
>  ce36208 
>   
> ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/configuration/hive-env.xml
>  be79331 
>   
> ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/scripts/hive.py
>  6cd6d35 
>   ambari-server/src/main/resources/stacks/HDP/2.1/services/stack_advisor.py 
> ad35688 
>   ambari-server/src/main/resources/stacks/HDP/2.2/services/stack_advisor.py 
> 7ef5fad 
>   ambari-server/src/test/python/stacks/2.1/common/test_stack_advisor.py 
> f9fb1f5 
>   ambari-server/src/test/python/stacks/2.6/common/test_stack_advisor.py 
> 2d7322d 
> 
> 
> Diff: https://reviews.apache.org/r/58568/diff/1/
> 
> 
> Testing
> -------
> 
> mvn clean test
> 
> 
> Thanks,
> 
> Vitalyi Brodetskyi
> 
>

Reply via email to