[ https://issues.apache.org/jira/browse/SENTRY-1626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15951262#comment-15951262 ]
Alexander Kolbasov commented on SENTRY-1626: -------------------------------------------- How would this work for upgrades? Are we going to change the schema for existing columns? This will make things backwards incompatible - for example we wouldn't be able to downgrade the version. > 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 > > Attachments: SENTRY-1626.000-sentry-ha-redesign.patch > > > 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)