Fixed Issues in Oozie
This section lists the issues that have been fixed since the previous version.
- CDPD-11967: Fix to address CWE-693: Protection Mechanism Failure
- CDPD-12742: Oozie is unable to communicate with ID Broker and fails to obtain a delegation token because of a missing Jar.
- This issue is now resolved.
- CDPD-13702: Fix to address CVE-2020-13692
- CDPD-14600: Fix to address CVE-2016-3088
- CDPD-14964: https://issues.apache.org/jira/browse/OOZIE-3592: When a Java action calls System.exit(), an exception is logged by Oozie for Sqoop actions even after successful workflow actions.
- This issue is now resolved.
- CDPD-12283: https://issues.apache.org/jira/browse/OOZIE-3529: By Oozie did not allow to use s3a and abfs file systems and users had to manually specify the supportability of these via Safety Valve
- Since Oozie is compatible with these filesystems we changed the default Oozie configuration to allow these so users dont have to manually specify it.
- CDPD-10746: Fix to address CVE-2019-17571
- CDPD-9895: https://issues.apache.org/jira/browse/OOZIE-3529: Various errors when trying to use an S3 filesystem
- Oozie is now fully compatible with S3.
- CDPD-9761: https://issues.apache.org/jira/browse/OOZIE-3584: There is a sub workflow run in independent mode that runs a fork action which contains two (or more) actions
- These actions inside the fork action run in parallel mode, and they have some seconds delay in between them. If a parameter is passed to one of these actions, that cannot be resolved, then it changes its status to FAILED, and also the workflows state to FAILED. The other actions state which are not started yet will stuck in PREP state forever. The correct behaviour would be to KILL the remaining actions as well as the workflow. Note: this bug only occurs when it is run in independent mode. If it has a parent workflow, then the parent workflow will kill this workflow after 10 minutes because of the callback process.
- CDPD-9721: Upgrade built-in spark-hive in Oozie
- Oozie is using the Spark-Hive library from the stack.
- CDPD-9220: https://issues.apache.org/jira/browse/OOZIE-3586: Oozie spark actions using --keytab fail due to duplicate dist. cache
- Oozie spark actions add everything in the distributed cache of the launcher job to the distributed cache of the spark job, meaning the keytab is already there, then the --keytab argument tries to add it again causing the failure.
- CDPD-9189: Apache Pig support was completely removed from Oozie
- CDPD-7108: https://issues.apache.org/jira/browse/OOZIE-3561: In case we have a workflow which has, lets say, 80 actions after each other, then the validator code "never" finishes
- CDPD-7107: https://issues.apache.org/jira/browse/OOZIE-3551: The following were added to the spark opts section of the spark action: --conf spark
- CDPD-7106: https://issues.apache.org/jira/browse/OOZIE-2828: query tag is not functional for Hive2 action node in oozie
- Workflow is intended to create a hive table using Hive2 action node. Though workflow run successfully, table is not created.
- CDPD-7105: https://issues.apache.org/jira/browse/OOZIE-2626: Oozie workflow processing becomes slow after the increase of rows in WF_JOBS and WF_ACTIONS tables when running against SQL Server
- CDPD-6877: https://issues.apache.org/jira/browse/OOZIE-3578: When you create a MapReduce action which then creates more than 120 counters, an exception was thrown
- CDPD-6630: https://issues.apache.org/jira/browse/OOZIE-3575: Oozie by default gathers delegation tokens for the nodes defined in MapReduce
- CDPD-5168: https://issues.apache.org/jira/browse/OOZIE-3381: Logging enhancements in CoordElFunctions for better supportability
- CDPD-4826: Oozies web server does not work when TLS is enabled and Open JDK 11 is in use
- This issue is now fixed.
- CDPD-12142: https://issues.apache.org/jira/browse/OOZIE-3516: Addressed the "Does not contain a valid host:port authority: yarnRM" warning in the logs
- This issue is now fixed.
