[
https://issues.apache.org/jira/browse/SENTRY-1856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vamsee Yarlagadda updated SENTRY-1856:
--------------------------------------
Resolution: Fixed
Status: Resolved (was: Patch Available)
5842648ccd01e143571b6950ca50f0abbffada84
Thanks Lina for the patch.
Thanks Sasha, Kalyan for the reviews.
> Persisting HMS snapshot and the notification-id to database in same
> transaction
> -------------------------------------------------------------------------------
>
> Key: SENTRY-1856
> URL: https://issues.apache.org/jira/browse/SENTRY-1856
> Project: Sentry
> Issue Type: Sub-task
> Components: Sentry
> Affects Versions: 2.0.0
> Reporter: kalyan kumar kalvagadda
> Assignee: Na Li
> Fix For: 2.0.0
>
> Attachments: SENTRY-1856.001.patch, SENTRY-1856.002.patch,
> SENTRY-1856.002.patch, SENTRY-1856.003.patch
>
>
> Currently notification-id associated with the snapshot and the actual HMS
> snapshot are persisted into database in a separate transactions.
> Ideally they should be updated in same transaction.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
