[
https://issues.apache.org/jira/browse/SENTRY-1803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergio Peña updated SENTRY-1803:
--------------------------------
Attachment: SENTRY-1803.1.patch
Seems the solution is simple. We just needed to remove the primary keys for
NOTIFICATION_ID from the tables used. The rest is correctly handled.
> HMSFollower should handle the case of multiple notifications with the same ID
> -----------------------------------------------------------------------------
>
> Key: SENTRY-1803
> URL: https://issues.apache.org/jira/browse/SENTRY-1803
> Project: Sentry
> Issue Type: Sub-task
> Components: Sentry
> Affects Versions: 2.0.0
> Reporter: Alexander Kolbasov
> Assignee: Sergio Peña
> Fix For: 2.0.0
>
> Attachments: SENTRY-1803.1.patch
>
>
> According to HIVE-16886, it is possible that HMSFollower will encounter
> multiple events with the same notification ID. It should do something sane in
> this case.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
