Uploaded image for project: 'Tech Debt'
  1. Tech Debt
  2. DEBT-1

No optimistic locking/update conflict resolution

    XMLWordPrintable

Details

    Description

      Reliability of the system, data consistency

      How to handle concurrent (conflicting) updates to records?

      UXPROD-1752 not in MVP List (row 499). Lobby for this to be included in Q1 or Q2 of 2020. It's important but may not outweigh other functional features/work. May implement as a "client opt-in" manner.

      Update July 17 2019: No activity to date. Discussion about deprioritizing since some have indicated it's not abnormal or not a big problem. Others, though, feel it's an expectation when coming from a traditional client-server SQL-based solution. Decided to leave a 'High' for several reasons.

      Attachments

        Issue Links

          relates to

          Task - A task that needs to be done. FOLIO-2028 SPIKE: how to handle update conflicts?

          • P3 - low priority level, item will be considered for inclusion in the next dev cycle
          • Closed

          New Feature - New feature requests MODINVSTOR-713 Enable support for optimistic locking (failOnConflict) in instances/holdings/items (part1)

          • P2 - normal priority level, must be included in the current development cycle
          • Closed

          Task - A task that needs to be done. RMB-719 SPIKE: design protocol and implementation for optimistic locking

          • P2 - normal priority level, must be included in the current development cycle
          • Closed

          New Feature - New feature requests RMB-727 Implement support for optimistic locking

          • P2 - normal priority level, must be included in the current development cycle
          • Closed

          New Feature - New feature requests UXPROD-1752 Prevent update conflicts (via optimistic locking): platform support for detection

          • P3 - low priority level, item will be considered for inclusion in the next dev cycle
          • Closed

          New Feature - New feature requests UXPROD-2796 Prevent update conflicts when doing manual edits (User A and User B)

          • P3 - low priority level, item will be considered for inclusion in the next dev cycle
          • Closed

          New Feature - New feature requests UXPROD-2797 Prevent update conflicts (1 user and system trying to act on the same record)

          • P3 - low priority level, item will be considered for inclusion in the next dev cycle
          • Closed

          New Feature - New feature requests UXPROD-2798 Prevent update conflicts (two automated processes acting on the same record)

          • P3 - low priority level, item will be considered for inclusion in the next dev cycle
          • Closed

          Activity

            People

              jakub Jakub Skoczen
              zburke Zak_Burke
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: