[ https://issues.apache.org/jira/browse/RANGER-798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gautam Borad updated RANGER-798: -------------------------------- Attachment: (was: RANGER-798.patch) > Handle different timezone issue while saving audit logs to Solr > --------------------------------------------------------------- > > Key: RANGER-798 > URL: https://issues.apache.org/jira/browse/RANGER-798 > Project: Ranger > Issue Type: Bug > Components: admin, audit > Affects Versions: 0.5.0 > Reporter: Gautam Borad > Assignee: Gautam Borad > Fix For: 0.5.2, 0.6.0 > > Attachments: > 0001-RANGER-798-Handle-different-timezone-issue-while-sav.patch > > > *Problem Statement* : > Currently audit event timestamp is converted to UTC timestamp at Plugin end > and then it is sent to audit stores, Since Date object picks local timezone > info from System, local timezone info is passed to Solr rather than UTC. > Since Solr engine does the conversion of all received Date object to UTC > timestamp, due to mismatched timezone info, Solr again does the conversion on > received timestamp, which leads to insertion of wrong event timestamp. if any > user tries to search any audit event log then he might not get the expected > result or audit logs of provided event. > *Proposed Solution* : > Send new Date object value as audit event time to Solr Doc, if audit store is > Solr. -- This message was sent by Atlassian JIRA (v6.3.4#6332)