Reduce complexity of suspension state check in job query

XMLWordPrintable

    • Type: Task
    • Resolution: Fixed
    • Priority: L3 - Default
    • 7.4.0, 7.4.0-alpha3
    • Affects Version/s: 7.3.1
    • Component/s: engine
    • Environment:
      Camunda BPM 7.3.X
      WebSphere
      DB2

      The job acquisition query selects only active jobs. For reasons of backwards compatibility, an active job has SUSPENSION_STATE_ = 1 or SUSPENSION_STATE_ is null. This additional null check makes the acquisition query more complex, posing problems on some databases for index usage.

      AT:

      • the SUSPENSION_STATE_ column is declared NOT NULL and has a default value 1 (active)
      • the job acquisition query no longer performs a null check for SUSPENSION_STATE_

        This is the controller panel for Smart Panels app

              Assignee:
              Unassigned
              Reporter:
              Matthijs
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: