What's New in Apache Oozie

Learn about the new features of Kudu in Cloudera Runtime 7.1.9.

Spark 3 support in Oozie
Oozie introduced the new Spark 3 based Spark 3 actions. For more information, see Spark 3 support in Oozie.
Make hive-site.xml, hbase-site.xml and sqoop-site.xml available for all Oozie actions
Now Oozie automatically copies the hive-site.xml, hbase-site.xml, and sqoop-site.xml to all action's classpath. For more information, see Oozie and client configurations.
Improve Oozie's app state action checking
Enhanced Oozie's action state checking, to immediately query for running applications right after start-up.
Oozie should upload and use the config files from sqoop-conf/managers.d when available
Previously, Oozie did not honor Sqoop's managers.d configurations and extra connector Jars from the lib folder, but now both are automatically available in Oozie's Sqoop action, allowing users to seamlessly utilize connectors like the Sqoop Teradata connector without the need for manual configuration updates or copying Jars to the Workflow's lib folder.
Oozie should not rely on its LoadBalancer internally
Oozie will no longer use the LoadBalancer to issue a callback notification, but instead it will try all available Oozie instances one-by-one. If the callback succeeded against one of the Oozie instances, then we will not try the other ones. This way the LoadBalancer will not be used for such purposes.
Cloudera Manager will provide the address of all Oozie server instances as a configuration to all Oozie instances. This will be then used by Oozie's callback mechanism so that instead of making the callback through the LoadBalancer in HA mode, the callback will be attempted through each Oozie instance, and if one of them succeeds, then we stop. This way we'll no longer use the LoadBalancer, and make the callback mechanism safer by not having a middle-man.
Handle Sqoop Teradata Connector parcels installation and configuration for Oozie
When you install a Sqoop Teradata connector parcel, Cloudera Manager will automatically make the necessary Jars and configuration available to Oozie's Sqoop action.
TCPS support for Oozie with Oracle DB backend
When it comes to configuring database connections, simply providing a hostname, port, username, and password may not be sufficient. In order to optimize Oozie's database connection, you might need to manually construct lengthy connection and configuration strings using safety-valve settings. To simplify this process and enable finer control over Oozie's database connection, you can use several enhancements. For more information, see Fine-tuning Oozie's database connection.
JDK 17 support
In supporting Java 17, certain applications which are executed with Oozie might require reflective access to internal Java classes, packages, or modules. To enable reflective access, you need to use the add-opens Java parameter. For more information, see Oozie Java-based actions with Java 17.