Fixed Issues — ODP 1.3.1.0
Issue Tracking
ODP issues are tracked via the Clemlab GitHub repository. Each issue is assigned an ODP identifier (e.g., ODP-NNN) and linked to the relevant upstream Apache JIRA or pull request where applicable.
If you encounter a problem not listed here, please file an issue at https://github.com/clemlabprojects with reproduction steps, cluster version details, and relevant log excerpts.
Key Fixes in ODP 1.3.1.0
Knox — JDK 21 Support (ODP-365)
Issue: Apache Knox failed to start when the cluster JDK was set to JDK 21 due to removed internal Java APIs (sun.misc.BASE64Encoder) that Knox depended on in earlier builds.
Fix: ODP 1.3.1.0 includes an updated Knox build that replaces deprecated internal API usages with their standard java.util.Base64 equivalents, enabling Knox to run correctly under JDK 21.
Impact: Clusters using JDK 21 (required for newer RHEL 9 / Rocky Linux 9 environments) can now deploy Knox without workarounds.
| Field | Value |
|---|---|
| ODP Issue | ODP-365 |
| Component | Apache Knox |
| Affected versions | ODP 1.3.0.x with JDK 21 |
| Fixed in | ODP 1.3.1.0 |
Ranger — Audit Logging for Apache NiFi (ODP-361)
Issue: Ranger audit events from Apache NiFi were not being forwarded to the configured audit store (Solr or HDFS) due to a misconfiguration in the NiFi Ranger plugin initialization sequence introduced in ODP 1.3.0.x.
Fix: The NiFi Ranger plugin is now correctly initialized at NiFi startup, and audit events are reliably sent to the Ranger audit backend.
Impact: Clusters requiring NiFi audit trails for compliance or security monitoring should upgrade to ODP 1.3.1.0.
| Field | Value |
|---|---|
| ODP Issue | ODP-361 |
| Component | Apache Ranger, Apache NiFi |
| Affected versions | ODP 1.3.0.x |
| Fixed in | ODP 1.3.1.0 |
HBase — Shaded Client Java 21 Compatibility
Issue: The HBase shaded client JAR shipped with ODP 1.3.0.x used internal Java APIs that were removed in JDK 17+ and caused InaccessibleObjectException errors at runtime when client applications were compiled and executed under JDK 21.
Fix: The HBase shaded client has been recompiled with JDK 21-compatible settings, removing all usages of removed internal APIs and adding appropriate module-info declarations.
Impact: Java applications using the HBase client on JDK 21 (e.g., Spark jobs, custom ETL tools) will work correctly without requiring --add-opens JVM flags.
| Field | Value |
|---|---|
| Component | Apache HBase shaded-client |
| Affected versions | ODP 1.3.0.x with JDK 21 |
| Fixed in | ODP 1.3.1.0 |