Uploaded image for project: 'Oozie'
  1. Oozie
  2. OOZIE-3406 [Umbrella] Reimplement Purge Service
  3. OOZIE-3400

[core] Fix PurgeService sub-sub-workflow checking

VotersWatch issueWatchersLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Sub-task
    • Status: Closed
    • Major
    • Resolution: Fixed
    • trunk
    • 5.2.0
    • core
    • None

    Description

      Purge service checks sub-workflows before it deletes a workflow. If some of the sub-workflows is not yet ready to be purged it does not delete the workflow. Several unit tests also checks this, e. g. testPurgeWFWithSubWF1.

      This check is recursive, it also checks sub-sub-workflows, sub-sub-sub-workflows....

      The recursive check is buggy. Let's assume that we have a workflow (A) with a single sub-workflow (B), which also has a sub-sub-workflow (C). If A is ready to be purged, B is ready to be purged, and C is not ready to be purged then the current implementation correctly recognizes that C and B is not purgeable, but it purges A. Instead of this, it should also recognize that it's not possible to purge A.

      Attachments

        1. OOZIE-3400-03.patch
          24 kB
          Andras Salamon
        2. OOZIE-3400-02.patch
          21 kB
          Andras Salamon
        3. OOZIE-3400-01.patch
          13 kB
          Andras Salamon
        4. OOZIE-3400-00.patch
          4 kB
          Andras Salamon

        Issue Links

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            asalamon74 Andras Salamon
            asalamon74 Andras Salamon
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment