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

Configuration properties from global section is not getting set in Hadoop job conf when using sub-workflow action in Oozie workflow.xml

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • None
    • 4.3.0
    • action
    • None

    Description

      When submitting Oozie workflow with sub-workflow action and with global section, configuration properties defined in global section is not getting set in launched Hadoop job conf. But when we use Pig or MR action in workflow.xml, configuration properties from global section set properly into Hadoop job conf.

      Attachments

        1. OOZIE-2030-v12.patch
          18 kB
          Jaydeep Vishwakarma
        2. OOZIE-2030-v11.patch
          18 kB
          Jaydeep Vishwakarma
        3. OOZIE-2030-v10.patch
          18 kB
          Jaydeep Vishwakarma
        4. OOZIE-2030-v9.patch
          19 kB
          Jaydeep Vishwakarma
        5. OOZIE-2030-v8.patch
          18 kB
          Jaydeep Vishwakarma
        6. OOZIE-2030-v8.patch
          18 kB
          Jaydeep Vishwakarma
        7. OOZIE-2030-v7.patch
          12 kB
          Jaydeep Vishwakarma
        8. OOZIE-2030-v6.patch
          10 kB
          Jaydeep Vishwakarma
        9. OOZIE-2030-v5.patch
          10 kB
          Jaydeep Vishwakarma
        10. OOZIE-2030-v4.patch
          18 kB
          Jaydeep Vishwakarma
        11. OOZIE-2030-v3.patch
          11 kB
          Jaydeep Vishwakarma
        12. OOZIE-2030-v2.patch
          36 kB
          Shwetha GS
        13. OOZIE-2030.patch
          22 kB
          Shwetha GS

        Issue Links

          blocks

          Improvement - An improvement or enhancement to an existing feature or task. FALCON-510 Inject falcon related properties to job conf

          • Major - Major loss of function.
          • Open
          breaks

          Bug - A problem which impairs or prevents the functions of the product. OOZIE-2441 SubWorkflow action with propagate-configuration but no global section throws NPE on submit

          • Blocker - Blocks development and/or testing work, production could not run
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. OOZIE-2511 SubWorkflow missing variable set from option if config-default is present in parent workflow

          • Major - Major loss of function.
          • Closed
          relates to

          New Feature - A new feature of the product, which has yet to be developed. OOZIE-2187 Add a way to specify a default JT/RM and NN

          • Major - Major loss of function.
          • Closed
          links to

          Web Link review board

          Activity

            People

              jaydeepvishwakarma Jaydeep Vishwakarma
              peeyushb Peeyush Bishnoi
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: