[
https://issues.apache.org/jira/browse/RANGER-900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15240570#comment-15240570
]
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/12798645/RANGER-900-2.patch
against master revision da3a323.
{color:red}-1 patch{color}. master compilation may be broken.
Console output:
https://builds.apache.org/job/PreCommit-RANGER-Build/158//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
>
>
> 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)
