[
https://issues.apache.org/jira/browse/SENTRY-1854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16095506#comment-16095506
]
Hadoop QA commented on SENTRY-1854:
-----------------------------------
Here are the results of testing the latest attachment
https://issues.apache.org/jira/secure/attachment/12878264/SENTRY-1854.001-sentry-ha-redesign.patch
against sentry-ha-redesign.
{color:red}Overall:{color} -1 due to 11 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
{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
{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
{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
{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/3082/console
This message is automatically generated.
> HMSFollower should handle notifications even if HDFS sync is disabled.
> ----------------------------------------------------------------------
>
> Key: SENTRY-1854
> URL: https://issues.apache.org/jira/browse/SENTRY-1854
> Project: Sentry
> Issue Type: Sub-task
> Components: Sentry
> Affects Versions: sentry-ha-redesign
> Reporter: Na Li
> Assignee: Na Li
> Fix For: sentry-ha-redesign
>
> Attachments: SENTRY-1854.001-sentry-ha-redesign.patch
>
>
> Currently, Sentry does not start HMSFollower when HDFS sync is disabled. This
> breaks PERM sync. For example, when a table/database is dropped, its
> permission should be removed when perm sync is enabled. Without HMSFollower,
> Sentry does not know when table/database is dropped, and therefore, cannot
> remove the permission accordingly.
> Sentry needs to make updates to have the follow behavior
> 1) When HDFS sync is disabled + PERM sync is disabled, do not start
> HMSFollower
> 2) when HDFS sync is enabled or PERM sync is enabled, start HMSFollower
> (Sentry change).
> 3) when HDFS sync is enabled, we save path change and perm change. nothing
> more.
> 4) when perm sync is enabled, we update perm when table/database is created,
> dropped or altered, nothing more.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
