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

resolveInstanceRange doesn't work for EL extensions

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

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • trunk
    • 4.0.0
    • None

    Description

      I have an EL extension today(0,0) which maps to start day of nominal time. This is used to specify startInstance, endInstance and instance in dataIn and dataOut of coordinator.

      In CoordCommandUtils.resolveInstanceRange(), getInstanceNumber has to return the instance number with respect to current. So, for coord-action-create-inst context, I have mapped today to current and hence getInstanceNumber returns the correct number. But later in resolveInstanceRange(), getFuncType is called with startInstance value which is today in this case and it maps to UNEXPECTED and throws up. getFuncType should be passed the evaluation of coord-action-create-inst context

      Attachments

        1. OOZIE-674.patch
          2 kB
          Shwetha GS
        2. OOZIE-674-v3.patch
          19 kB
          Shwetha GS
        3. OOZIE-674-v4.patch
          17 kB
          Shwetha GS
        4. OOZIE-674-v5.patch
          20 kB
          Shwetha GS
        5. OOZIE-674-v6.patch
          21 kB
          Shwetha GS
        6. OOZIE-674-ver2.patch
          20 kB
          Shwetha GS

        Activity

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

          People

            shwethags Shwetha GS
            shwethags Shwetha GS
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment