Uploaded image for project: 'Sentry (Retired)'
  1. Sentry (Retired)
  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

    • Sub-task
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • 2.0.0
    • 2.0.0
    • Sentry
    • 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

          links to

          Web Link Review Link for this case

          Activity

            People

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

              Dates

                Created:
                Updated:
                Resolved: