Ramesh Mani created RANGER-1105:
-----------------------------------
Summary: Ranger should provide configuration to have do hdfs audit
file roll over at absolute time
Key: RANGER-1105
URL: https://issues.apache.org/jira/browse/RANGER-1105
Project: Ranger
Issue Type: Bug
Affects Versions: 0.7.0
Reporter: Ramesh Mani
Assignee: Ramesh Mani
Ranger should provide configuration to have do hdfs audit file roll over at
absolute time. Currently parameter
"xasecure.audit.destination.hdfs.file.rollover.sec" is used for rollover and
the files are closed on relative time using this value from the start of the
component. Instead we provide
"xasecure.audit.destination.hdfs.file.rollover.period" which take time period
with suffix -"m" - minutes, "h" - hours , "d" - days , "w" - weeks, "M" -
month, "y" -years.
eg.
if xasecure.audit.destination.hdfs.file.rollover.period - 1d - ranger audit
file in hdfs would be rolled over at 1 day window i.e file will be closed
exactly at 23:59:59 hour for that day and a new file will be opened for
00:00:00 hour. In this way we have file content which is exactly for that time
period window in this case 1 day.
xasecure.audit.destination.hdfs.file.rollover.period - 1d for 1 day rollover
period
xasecure.audit.destination.hdfs.file.rollover.period - 2 d for 2 day rollover
period
xasecure.audit.destination.hdfs.file.rollover.period - 10m for every 10
minutes rollover period.
xasecure.audit.destination.hdfs.file.rollover.period - 1w for every week
rollover window
xasecure.audit.destination.hdfs.file.rollover.period -1M for one month
rollover window.
if this is param is not specified, it uses
"xasecure.audit.destination.hdfs.file.rollover.sec" to compute the absolute
window.
By default this is 1day meaning if both the parameters are not specified the
rollover window would be 1day.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
