Fixed Issues in Apache Oozie

Review the list of Oozie issues that are resolved in Cloudera Runtime 7.2.14.

CDPD-21874: Oozie should be able to handle file-system credentials coming from various places in the workflow.xml.

This issue is resolved.

CDPD-30584: The Oozie client will display the full stacktrace in case it fails to connect to the Oozie server.

This issue is resolved.

CDPD-30045: Oozie's ZooKeeper related codebase now has extra trace level logging entries so in case of any ZooKeeper related issues these can be enabled. Affected classes: org.apache.oozie.command.XCommand org.apache.oozie.service.ZKLocksService

This issue is resolved.

OPSAPS-57546: All form factors. When the Knox gateway is available on the cluster and it’s discovery is enabled for Oozie then the Web UI link of Oozie through Knox will appear among the direct links.

This issue is resolved.

OPSAPS-62019: Enabled thread level logging for Oozie server by adding "%t" in log4j properties in Oozie configs.

This issue is resolved.

CDPD-28768: Actions are stuck while running in a Fork-Join workflow.

This issue is resolved.

CDPD-30426: Correct maximum wait time between database retry attempts property.

The oozie-default.xml had a default value for controlling the JPA retry wait time. The name of the property in the oozie-default.xml was: oozie.service.JPAService.retry.maximum-wait-time.ms. However, the Oozie server was looking for a property named oozie.service.JPAService.maximum-wait-time.ms. This is now fixed and the oozie-default.xml and the Oozie server are now in sync. In case you put an override as a safety-valve with a name oozie.service.JPAService.maximum-wait-time.ms, then Oozie will prefer that.

OPSAPS-61115: Implement a new checkbox for Oozie to disable the Oozie UI

A new checkbox was implemented on the Oozie configuration page which can be used to turn off the Oozie UI completely. Meaning none of the Oozie UI resources will be served and thus if you are worried about JQuery vulnerabilities, etc. which cannot be fixed short term, you can use this feature to get rid of these by not exposing these at all.

CDPD-27661: Implement a way to disable the Oozie UI

There is a new property named "oozie.ui.enabled" users can set for Oozie with a value true of false. By default it's set to true. When set to false, the Oozie UI will be complete disabled, the Oozie server will not even expose the UI resources, hence this can be a workaround for the JQuery vulnerabilities.

CDPD-19654: The Console URL on the web UI is not a Knox URL.

The Console URL for Yarn on the Oozie UI will be a Knox URL when the Oozie UI is accessed through Knox.

CDPD-30487: Improve getActionData in Oozie.

The Yarn application launched by Oozie creates a file for storing action related information which will be read by the Oozie server. In case the Yarn application is able to create this file, but won't be able to put the necessary data into it and so the file remains empty, the Oozie server will fail to parse this file. This error is now fixed.