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

Schema config properties should be consistent with ActionExecutor config properties

    XMLWordPrintableJSON

    Details

    • Type: Improvement
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: trunk
    • Fix Version/s: 4.2.0
    • Component/s: core
    • Labels:
      None

      Description

      For specifying ActionExecutors, we have oozie.service.ActionService.executor.classes and oozie.service.ActionService.executor.ext.classes. The former specifies the default ones, and the latter allows adding/overriding them.

      For specifying the corresponding action schemas, we have just: oozie.service.SchemaService.wf.ext.schemas. This makes it difficult for users to add/override schemas. We should add a oozie.service.SchemaService.wf.schemas with the default schemas, where the "ext" config would add/override. This should be backwards compatible because both properties get loaded. We can also remove the workflow schemas from being hardcoded in the SchemaService class.

      Similarly, we should do the same for the coordinators, bundles, and sla schema properties.

        Attachments

        1. OOZIE-2107.patch
          10 kB
          Robert Kanter
        2. OOZIE-2107.patch
          10 kB
          Robert Kanter

          Activity

            People

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

              Dates

              • Created:
                Updated:
                Resolved: