[ https://issues.apache.org/jira/browse/AMBARI-18348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15475398#comment-15475398 ]
Hadoop QA commented on AMBARI-18348: ------------------------------------ {color:red}-1 overall{color}. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12827664/AMBARI-18348.patch against trunk revision . {color:red}-1 patch{color}. The patch command could not apply the patch. Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/8624//console This message is automatically generated. > 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)