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

rangerqa commented on RANGER-900:
---------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment
  http://issues.apache.org/jira/secure/attachment/12798788/RANGER-900-3.patch
  against master revision 80e2eae.

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

    {color:green}+1 tests included{color}.  The patch appears to include 2 new 
or modified test files.

    {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:red}-1 release audit{color}.  The applied patch generated 1 
release audit warnings.

    {color:red}-1 core tests{color}.  The test build failed in  

Test results: 
https://builds.apache.org/job/PreCommit-RANGER-Build/161//testReport/
Release audit warnings: 
https://builds.apache.org/job/PreCommit-RANGER-Build/161//artifact/patchprocess/patchReleaseAuditProblems.txt
Console output: 
https://builds.apache.org/job/PreCommit-RANGER-Build/161//console

This message is automatically generated.

> Remove support for DB based auditing
> ------------------------------------
>
>                 Key: RANGER-900
>                 URL: https://issues.apache.org/jira/browse/RANGER-900
>             Project: Ranger
>          Issue Type: New Feature
>            Reporter: Velmurugan Periasamy
>            Assignee: Pradeep Agrawal
>             Fix For: 0.6.0
>
>         Attachments: RANGER-900-1.patch, RANGER-900-2.patch, 
> RANGER-900-3.patch
>
>
> Currently Ranger supports the following methods for storing audit data
> 1. Database
> 2. HDFS
> 3. Solr
> 4. Log4j custom appender
> Ranger UI can currently read from both database and Solr. Since storing audit 
> data in database in not a scalable approach, proposal is to remove database 
> support for audit and keep only Solr as the source of audit for Ranger UI. 
> Users can still send their audit to HDFS as well as Log4j.
> https://issues.apache.org/jira/browse/RANGER-271 provides a migration utility 
> for moving data from DB to Solr. 



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

Reply via email to