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

'oozie validate' command should be moved server-side


    • Type: New Feature
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: trunk
    • Fix Version/s: 4.3.0
    • Component/s: None
    • Labels:


      The oozie validate command runs an XML validator against a workflow, coordinator, or bundle XML file to check that it's valid with any of the XSD schema files we have.

      Currently, this is implemented in the Oozie CLI (OozieCLI.validateCommand(...), which has some downsides:

      1. It's only available to OozieCLI users; anyone using the REST API can't use it
      2. It's currently hardcoded to the specific XSD files we ship with Oozie
        1. Whenever we add a new schema, we have to also manually update this, which is easy to forget
        2. Users can't validate custom schemas that the Oozie server would accept

      We should move this to the Oozie server, perhaps at a new "validate" endpoint. It should be able to accept a local file path (the current behavior) and perhaps also an HDFS file while we're at it. For the local XML file, it can just be uploaded as part of the REST call.

      Also, the description for the command needs to be updated to mention that it also handles coordinators and bundles.


        1. OOZIE-2159.6.patch
          63 kB
          Azrael Seoeun
        2. OOZIE-2159.5.patch
          62 kB
          Azrael Seoeun
        3. OOZIE-2159.4.patch
          61 kB
          Azrael Seoeun
        4. OOZIE-2159.3.patch
          61 kB
          Azrael Seoeun
        5. OOZIE-2159.2.patch
          46 kB
          Azrael Seoeun
        6. OOZIE-2159.1.patch
          39 kB
          Azrael Seoeun

          Issue Links



              • Assignee:
                seoeun25 Azrael Seoeun
                rkanter Robert Kanter
              • Votes:
                0 Vote for this issue
                4 Start watching this issue


                • Created: