You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ranger.apache.org by "Qiang Zhang (JIRA)" <ji...@apache.org> on 2017/06/08 06:53:18 UTC
[jira] [Updated] (RANGER-1604) DB based auditing had been removed
in RANGER-900. But some configurations and codes are not removed
accordingly in Ranger Admin. It often makes the user feel confused such as
RANGER-1286.
[ https://issues.apache.org/jira/browse/RANGER-1604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Qiang Zhang updated RANGER-1604:
--------------------------------
Attachment: 0001-RANGER-1604-DB-based-auditing-had-been-removed-in-RA.patch
> DB based auditing had been removed in RANGER-900. But some configurations and codes are not removed accordingly in Ranger Admin. It often makes the user feel confused such as RANGER-1286.
> -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: RANGER-1604
> URL: https://issues.apache.org/jira/browse/RANGER-1604
> Project: Ranger
> Issue Type: Bug
> Components: admin
> Affects Versions: 1.0.0
> Reporter: Qiang Zhang
> Assignee: Qiang Zhang
> Priority: Minor
> Labels: patch
> Fix For: 1.0.0
>
> Attachments: 0001-RANGER-1604-DB-based-auditing-had-been-removed-in-RA.patch
>
>
> DB based auditing had been removed in RANGER-900. But some configurations and codes are not removed accordingly in Ranger Admin. It often makes the user feel confused such as RANGER-1286. We should do the following modification:
> 1. Add description information to configuration file to remind users don't use db to store audit log..
> 2. Remove invalid code from setup.sh to eliminate misunderstanding. In order to avoid the introduction of the new issue, I do not modify db_setup.py and dba_script.py.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)