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


Ship it!




Ship It!

- Ankita Sinha


On April 29, 2017, 7:35 a.m., Pradeep Agrawal wrote:
> 
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/58871/
> -----------------------------------------------------------
> 
> (Updated April 29, 2017, 7:35 a.m.)
> 
> 
> Review request for ranger, Ankita Sinha, Don Bosco Durai, Gautam Borad, Abhay 
> Kulkarni, Madhan Neethiraj, Mehul Parikh, Ramesh Mani, Selvamohan Neethiraj, 
> Sailaja Polavarapu, and Velmurugan Periasamy.
> 
> 
> Bugs: RANGER-1550
>     https://issues.apache.org/jira/browse/RANGER-1550
> 
> 
> Repository: ranger
> 
> 
> Description
> -------
> 
> **Problem Statement :** Test connection is failing with below message on UI.
> Connection Failed.
> Unable to retrieve any files using given parameters, You can still save the 
> repository and start creating policies, but you would not be able to use 
> autocomplete for resource names. Check ranger_admin.log for more info.
> java.lang.NullPointerException.
> 
> ** Proposed Solution:**  HIVE_SITE_FILE_PATH property is set to null at line 
> 152 of HadoopConfigHolder.java. we need to set it blank or have null check 
> before reading the file everywhere otherwise while reading the file directly 
> may cause nullpointer exception. I have set the properties value to blank for 
> now. 
> Note : Implementation can be changed if the proposed approach is not good and 
> there is a better way to solve this issue.
> 
> 
> Diffs
> -----
> 
>   
> agents-common/src/main/java/org/apache/ranger/plugin/client/HadoopConfigHolder.java
>  928398d 
> 
> 
> Diff: https://reviews.apache.org/r/58871/diff/1/
> 
> 
> Testing
> -------
> 
> Checked test Connection of HDFS, HIVE and Hbase service.
> 
> 
> Thanks,
> 
> Pradeep Agrawal
> 
>

Reply via email to