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

Refactor SentryStore transaction management to allow for extra TransanctionBlocks for a single permission update

    XMLWordPrintableJSON

Details

    • Sub-task
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • 2.0.0
    • 2.0.0
    • Sentry

    Description

      To persist single permission change, it needs to combine multiple things in a single transaction:

      • Doing the actual operation (priv change)
      • Updating notification ID.

      It is important to do this in a single transaction to guarantee that notificationID handling is atomic. Current code structure doesn't allow for that.

      So we need to pass extra transaction code to SentryStore functions or figure out a generic way to do this.

      Attachments

        Issue Links

          blocks

          Sub-task - The sub-task of the issue SENTRY-1539 HMS Follower should store arriving HMS notifications

          • Major - Major loss of function.
          • Resolved
          is required by

          Sub-task - The sub-task of the issue SENTRY-1608 Converting Sentry to a stateless service

          • Major - Major loss of function.
          • Resolved
          relates to

          Sub-task - The sub-task of the issue SENTRY-1511 HDFS Sync change for handling persisted Sentry delta or full updates

          • Major - Major loss of function.
          • Resolved
          links to

          Web Link Code Review Link

          Activity

            People

              hahao Hao Hao
              akolb Alex Kolbasov
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: