[
https://issues.apache.org/jira/browse/SENTRY-2422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17164095#comment-17164095
]
Hadoop QA commented on SENTRY-2422:
-----------------------------------
Here are the results of testing the latest attachment
https://issues.apache.org/jira/secure/attachment/13008327/SENTRY-2422.001.patch
against master.
{color:red}Overall:{color} -1 due to 2 errors
{color:red}ERROR:{color} mvn test exited 1
{color:red}ERROR:{color} Failed:
org.apache.sentry.hdfs.TestSentryHDFSServiceProcessor
Console output:
https://builds.apache.org/job/PreCommit-SENTRY-Build/4482/console
This message is automatically generated.
> HMS synchronization is causing multiple entries of the same ID in
> SENTRY_HMS_NOTIFICATION_ID
> --------------------------------------------------------------------------------------------
>
> Key: SENTRY-2422
> URL: https://issues.apache.org/jira/browse/SENTRY-2422
> Project: Sentry
> Issue Type: Improvement
> Components: Core
> Affects Versions: 2.1.0, 2.0.1
> Reporter: Brian Towles
> Assignee: Na Li
> Priority: Major
> Attachments: SENTRY-2422.001.patch, SENTRY-2422.001.patch
>
>
> When processing updates for the HMS notifications, multiple entries of the
> same ID are being put into the SENTRY_HMS_NOTIFICATION_ID table.
> This can be seen after doing a non location changing ALTER TABLE in hive for
> example.
>
> ALTER TABLE sometable SET TBLPROPERTIES ("someproperty"="somevalue");
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
