[
https://issues.apache.org/jira/browse/RANGER-1780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16180011#comment-16180011
]
Ramesh Mani commented on RANGER-1780:
-------------------------------------
Yes, I agree with [~bosco] on this, AuditSummaryQueue is generic for the all
the components which Ranger supports and changing its behavior has to be in
line with all other component's audit data format.
In this case, I feel there should be a function to generate the key at each
component level to do the aggregation, which can be part of ranger audit
configuration of the respective component.
> Allow AuditSummaryQueue to aggregate events in the same directory
> -----------------------------------------------------------------
>
> Key: RANGER-1780
> URL: https://issues.apache.org/jira/browse/RANGER-1780
> Project: Ranger
> Issue Type: Improvement
> Components: audit
> Affects Versions: 0.7.1
> Reporter: Alejandro Fernandez
> Assignee: Alejandro Fernandez
> Fix For: 1.0.0
>
> Attachments: RANGER-1780.patch, ranger_summary.png
>
>
> AuditSummaryQueue already has logic to enable the summarization, but it
> requires 2 events to have the exact same resource path (plus a couple of
> other fields such as user, access type, access result, action, client ip,
> session).
> This Jira is to add a config called
> xasecure.audit.provider.summary.aggregate.level so that if it is set to
> "directory" then 2 events can still be aggregated if they are files in the
> same directory.
> If the config is not specified its default value will be "file" which
> preserves the existing behavior.
> See [^ranger_summary.png] for screenshot on desired behavior.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
