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

rangerqa commented on RANGER-951:
---------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment
  http://issues.apache.org/jira/secure/attachment/12801391/RANGER-951-4.patch
  against master revision 3fa3de2.

    {color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

    {color:red}-1 tests included{color}.  The patch doesn't appear to include 
any new or modified tests.
                        Please justify why no new tests are needed for this 
patch.
                        Also please list what manual steps were performed to 
verify this patch.

    {color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

    {color:green}+1 javadoc{color}.  There were no new javadoc warning messages.

    +1 checkstyle.  The patch generated 0 code style errors.

    {color:green}+1 findbugs{color}.  The patch does not introduce any new 
Findbugs (version 2.0.3) warnings.

    {color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

    {color:green}+1 core tests{color}.  The patch passed unit tests in .

Test results: 
https://builds.apache.org/job/PreCommit-RANGER-Build/191//testReport/
Console output: 
https://builds.apache.org/job/PreCommit-RANGER-Build/191//console

This message is automatically generated.

> Modify ranger-admin to put stackdef for specified components
> ------------------------------------------------------------
>
>                 Key: RANGER-951
>                 URL: https://issues.apache.org/jira/browse/RANGER-951
>             Project: Ranger
>          Issue Type: Bug
>          Components: Ranger
>    Affects Versions: 0.6.0
>            Reporter: Pradeep Agrawal
>            Assignee: Pradeep Agrawal
>             Fix For: 0.6.0
>
>         Attachments: RANGER-951-4.patch
>
>
> Add a configuration in ranger-admin-site.xml that would specify:
> <property>
> <name>ranger.supportedcomponents</name>
> <value>storm,kafka,hbase</value>
> </property>
> When the parameter value is not empty, Ranger Admin bootstrap will load only 
> the specified component's Ranger stack-definitions. If the parameter does not 
> exist or empty, then all stack-definitions of all known components (HDFS, 
> Hive, HBase, Knox, Storm, YARN, Kafka, Solr, KMS) would be loaded during 
> bootstrap.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to