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 2017/07/20 20:30:00 UTC

[jira] [Created] (SENTRY-1856) Persisting HMS snapshot and the notification-id to database in same transaction

kalyan kumar kalvagadda created SENTRY-1856:
-----------------------------------------------

             Summary: 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: sentry-ha-redesign
            Reporter: kalyan kumar kalvagadda
             Fix For: sentry-ha-redesign


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)