You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@sentry.apache.org by "kalyan kumar kalvagadda (JIRA)" <ji...@apache.org> on 2018/10/25 19:02:00 UTC
[jira] [Commented] (SENTRY-2422) HMS syntonization is causing
multiple entries of the same ID in SENTRY_HMS_NOTIFICATION_ID
[ https://issues.apache.org/jira/browse/SENTRY-2422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16664157#comment-16664157 ]
kalyan kumar kalvagadda commented on SENTRY-2422:
-------------------------------------------------
Sentry is checking the SENTRY_PATH_CHANGE table to see if the event was processed. This is not correct as all the events are not recorded in SENTRY_PATH_CHANGE table. instead it should be checked in
SENTRY_HMS_NOTIFICATION_ID table.
> HMS syntonization 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.0.1
> Reporter: Brian Towles
> Assignee: kalyan kumar kalvagadda
> Priority: Major
>
> 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
(v7.6.3#76005)