[
https://issues.apache.org/jira/browse/SENTRY-1626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15946062#comment-15946062
]
Hadoop QA commented on SENTRY-1626:
-----------------------------------
Here are the results of testing the latest attachment
https://issues.apache.org/jira/secure/attachment/12860944/SENTRY-1626.000-sentry-ha-redesign.patch
against sentry-ha-redesign.
{color:red}Overall:{color} -1 due to 3 errors
{color:red}ERROR:{color} mvn test exited 1
{color:red}ERROR:{color} Failed:
org.apache.sentry.provider.db.service.persistent.TestSentryStore
{color:red}ERROR:{color} Failed:
org.apache.sentry.provider.db.service.persistent.TestSentryStore
Console output:
https://builds.apache.org/job/PreCommit-SENTRY-Build/2457/console
This message is automatically generated.
> 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)
