Uploaded image for project: 'Oozie'
  1. Oozie
  2. OOZIE-981

Subworkflow lib not found in classpath when parent workflow lib overwrites it

VotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 3.3.0
    • 3.3.0
    • None
    • None

    Description

      OOZIE-567 addresses the bug mentioned in the title here - by adding the subworkflow libpath to the classpath in addition to parent workflow libpath. OOZIE-871 reverted this to avoid duplicate values, but the subworkflow libpath should not be overwritten by parent workflow's libpath. Hence, tackling this bug here.

      Existing testcase modified slightly to demonstrate the expected behavior.

      Attachments

        1. OOZIE-981v1.patch
          6 kB
          Mona Chitnis
        2. OOZIE-981.patch
          2 kB
          Mona Chitnis

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

          People

            chitnis Mona Chitnis
            chitnis Mona Chitnis
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment