Uploaded image for project: 'Oozie'
  1. Oozie
  2. OOZIE-1881 Docs fixes
  3. OOZIE-2128

Clarify sub workflow "conflicting" jars

    XMLWordPrintableJSON

    Details

    • Type: Sub-task
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: docs
    • Labels:
      None

      Description

      The docs on subworkflows state:

      The subworkflow can inherit the lib jars from the parent workflow by setting oozie.subworkflow.classpath.inheritance to true in oozie-site.xml or on a per-job basis by setting oozie.wf.subworkflow.classpath.inheritance to true in a job.properties file. If both are specified, oozie.wf.subworkflow.classpath.inheritance has priority. If the subworkflow and the parent have conflicting jars, the subworkflow's jar has priority. By default, oozie.wf.subworkflow.classpath.inheritance is set to false.

      http://oozie.apache.org/docs/4.1.0/WorkflowFunctionalSpec.html#a3.2.6_Sub-workflow_Action

      We should clarify what we mean by "conflicting jars". The intention is jars with the same name (e.g. "foo.jar" in the parent workflow and "foo.jar" in the sub workflow). Some users may read this as two jars with conflicting classes, which we don't do anything about (e.g. "foo-1.0.jar" and "foo-2.0.jar").

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              rkanter Robert Kanter
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated: