[
https://issues.apache.org/jira/browse/AMBARI-18348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivér Szabó updated AMBARI-18348:
----------------------------------
Resolution: Fixed
Status: Resolved (was: Patch Available)
committed to trunk:
{code:java}
commit 8a1305325fe474ab7ee8e411440eef79031806aa
Author: Miklos Gergely <[email protected]>
Date: Mon Oct 3 16:13:08 2016 +0200
AMBARI-18348. Ranger audit log collection is not used in Log Search (Miklos
Gergely via oleewere)
Change-Id: I50b4c2c375d1657d620cfd1cab30943688ef079a
{code}
comitted to branch-2.5:
{code:java}
commit a941d1ec83b3de9899e04fd72e79f4001d36e311
Author: Miklos Gergely <[email protected]>
Date: Mon Oct 3 16:13:08 2016 +0200
AMBARI-18348. Ranger audit log collection is not used in Log Search (Miklos
Gergely via oleewere)
Change-Id: I50b4c2c375d1657d620cfd1cab30943688ef079a
{code}
> Ranger audit log collection is not used in Log Search (managed by ambari)
> -------------------------------------------------------------------------
>
> Key: AMBARI-18348
> URL: https://issues.apache.org/jira/browse/AMBARI-18348
> Project: Ambari
> Issue Type: Bug
> Affects Versions: 2.4.0
> Reporter: Miklos Gergely
> Assignee: Miklos Gergely
> Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-18348.patch
>
>
> Audit log collection and ranger audit log collection are 2 different
> collection with almost the same schema. With solr alias support, we can use
> both.
> Also use ambari audit logs inside audit collection, not in service log
> collection
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
