You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@sentry.apache.org by "Alexander Kolbasov (JIRA)" <ji...@apache.org> on 2017/02/24 22:46:44 UTC
[jira] [Commented] (SENTRY-1626) Tables contain createTime should
either remove it or update the time using SQL
[ https://issues.apache.org/jira/browse/SENTRY-1626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15883669#comment-15883669 ]
Alexander Kolbasov commented on SENTRY-1626:
--------------------------------------------
It is interesting to know how is this used - may be for ayditing? I agree that using DB for creation times is cleaner.
> Tables contain createTime should either remove it or update the time using SQL
> ------------------------------------------------------------------------------
>
> Key: SENTRY-1626
> URL: https://issues.apache.org/jira/browse/SENTRY-1626
> Project: Sentry
> Issue Type: Sub-task
> Components: Hdfs Plugin
> Affects Versions: sentry-ha-redesign
> Reporter: Lei (Eddy) Xu
> Assignee: Lei (Eddy) Xu
> Priority: Minor
> Fix For: sentry-ha-redesign
>
>
> Most of the table in Sentry contains createTime, e.g {{MSentryRole}}, {{MSentryGroup}}, {{MSentryPermChange}}, {{MSentryPrivilege}}, {{MAuthzPathsMapping}} and {{MSentryPathChange}}. Even though it is not used, it may be error-prone for future.
> The time between leader and standby servers might be different, so that after a failover, the newly elected leader might write changes with older {{createdTime}}.
> We can either remove this field, or update the time based in the database.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)