Uploaded image for project: 'Sentry'
  1. Sentry
  2. SENTRY-872 Uber jira for HMS HA + Sentry HA redesign
  3. SENTRY-1856

Persisting HMS snapshot and the notification-id to database in same transaction

    XMLWordPrintableJSON

    Details

    • Type: Sub-task
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 2.0.0
    • Fix Version/s: 2.0.0
    • Component/s: Sentry
    • Labels:
      None

      Description

      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.

        Attachments

        1. SENTRY-1856.001.patch
          20 kB
          Na Li
        2. SENTRY-1856.002.patch
          20 kB
          Na Li
        3. SENTRY-1856.002.patch
          20 kB
          Na Li
        4. SENTRY-1856.003.patch
          20 kB
          Na Li

          Issue Links

            Activity

              People

              • Assignee:
                linaataustin Na Li
                Reporter:
                kkalyan Krishna Kalyan
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: