You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@sentry.apache.org by "Lars Francke (JIRA)" <ji...@apache.org> on 2018/11/19 19:57:00 UTC

[jira] [Updated] (SENTRY-2422) HMS synchronization 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:all-tabpanel ]

Lars Francke updated SENTRY-2422:
---------------------------------
    Summary: HMS synchronization is causing multiple entries of the same ID in SENTRY_HMS_NOTIFICATION_ID  (was: HMS syntonization is causing multiple entries of the same ID in SENTRY_HMS_NOTIFICATION_ID)

> 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.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)