[ 
https://issues.apache.org/jira/browse/SENTRY-2065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

kalyan kumar kalvagadda updated SENTRY-2065:
--------------------------------------------
    Fix Version/s:     (was: 2.0.0)
                   2.1.0

Moving all unresolved jiras with fix version 2.0.0 to 2.1.0. Please change the 
fix version if you intend to make it into 2.0.0 release.


> Timestamp in MSentryPathChange and MSentryPermChange should be set by DB 
> server
> -------------------------------------------------------------------------------
>
>                 Key: SENTRY-2065
>                 URL: https://issues.apache.org/jira/browse/SENTRY-2065
>             Project: Sentry
>          Issue Type: Sub-task
>          Components: Sentry
>    Affects Versions: 2.0.0
>            Reporter: Na Li
>            Assignee: Na Li
>             Fix For: 2.1.0
>
>
> The timestamp of the path change and perm change entries should be set by DB 
> server, so when there are multiple sentry servers, the timestamp of the 
> entries are from the single source, i.e., no need to require the time sync 
> among sentry servers. When sentry retrieve those entries for HDFS, sentry can 
> retrieve the entries after the given timestamp from request.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to