Uploaded image for project: 'UX Product'
  1. UX Product
  2. UXPROD-2994

Optimistic Locking: coordinate rollout of "failOnConflict" to selected modules and APIs

    XMLWordPrintable

Details

    • Core: Platform
    • 0
    • R4
    • R1
    • R1
    • R1
    • R1

    Description

      How

      Optimistic Locking functionality in an RMB module is enabled for selected tables by changing configuration in the schema.json file. See https://github.com/folio-org/raml-module-builder#optimistic-locking. OL changes the behavior of the API and hence requires a major interface change.

      Where

      It has been discussed that OL 'failOnConflict' should be enabled for interfaces where there is a risk of concurrent access (and collisions). In mod-inventory storage this is done for instances/holdings/items.

      What

      POs: indicate interfaces where OL should be enabled by creating a specific backend issue and linking to this feature.

      TestRail: Results

        Attachments

          Issue Links

            defines

            Umbrella - UXPROD-3058 Optimistic Locking

            • TBD - To be determined
            • In progress
            is defined by

            Task - A task that needs to be done. MODINVSTOR-708 enable 'failOnConflict' for instances/holdings/items interfaces

            • P2 - normal priority level, must be included in the current development 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

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. MODNOTES-175 Optimistic locking for note_data

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

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. MODORDSTOR-225 Optimistic locking for pieces/po_line/purchase_order

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

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. MODORGSTOR-106 Optimistic locking for organizations/contacts/interfaces

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

            New Feature - New feature requests UXPROD-3089 Inventory. Implementing Optimistic Locking

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

            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

            Task - A task that needs to be done. UXPROD-3048 Check that generated sequences cannot produce duplicates

            • TBD - To be determined
            • Open

            New Feature - New feature requests UXPROD-3089 Inventory. Implementing Optimistic Locking

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

            Activity

              People

                Unassigned Unassigned
                jakub Jakub Skoczen
                Votes:
                0 Vote for this issue
                Watchers:
                12 Start watching this issue

                Dates

                  Created:
                  Updated:

                  TestRail: Runs

                    TestRail: Cases