Ranger 2.4.0.0 - 2310 (EEP 9.2.0) Release Notes
Apache Ranger is a tool to help you monitor and manage security for the Hadoop components that are included in the HPE Ezmeral Ecosystem Pack. For more information about the Data Fabric implementation of Ranger, see Ranger.
The notes below relate specifically to the HPE Ezmeral Data Fabric distribution of Apache Ranger. You may also be interested in the Apache Ranger home page and the Apache Ranger changelog.
These release notes contain only HPE-specific information and are not necessarily cumulative in nature. For information about how to use the release notes, see Ecosystem Component Release Notes.
| Version | 2.4.0.0 |
| Release Date | October 2023 |
| HPE Version Interoperability | See EEP Components and OS Support |
| Source on GitHub | https://github.com/mapr/ranger |
| GitHub Release Tag | 2.4.0.0-eep-920 |
| Maven Artifacts | https://repository.mapr.com/maven/ |
| Package Names | Navigate to http://package.ezmeral.hpe.com/releases/MEP/, and select your EEP (MEP) and OS to view the list of package names. |
New in this Release
EEP 9.2.0 updates the Ranger version to 2.4.0.
Installation
You can install Ranger by using manual steps or by using the Installer. See these
topics:
- Installing Ranger (manual steps)
- Installing Ranger Using the Installer
Fixes
This HPE release includes the following fixes on the base Apache release. For details,
refer to the commit log for this project in GitHub:
| GitHub Commit Number | Date (YYYY-MM-DD) | HPE Fix Number and Description |
| 5842bd28f | 2023-09-27 | RAN-302 Package uninstall throws ps errors |
| c24bd54ab | 2023-09-27 | RAN-301 Warden fails to start Ranger services on Compute node because of wrong permissions of warden.ranger-*.conf files set after configure.sh run |
| d2563521d | 2023-09-21 | RAN-289 db_override_connection_string doesn't work |
| 26cca4e74 | 2023-09-15 | (RAN-299) RAN-102 FIPS mode: keystore types (JCEKS -> BCFKS) (Part 2) (yarn) |
| 90d69fc98 | 2023-09-14 | RAN-294 Upgrade artifact naming to EEP v9.2.0 |
| c786b23d1 | 2023-09-14 | RAN-298 setup.sh run fails on cluster with enabled FIPS mode |
| bde16d562 | 2023-09-04 | RAN-291 Usersync: take jetty-util jar from hadoop-common |
Known Issues and Limitations
- Ranger and Mixed FIPS Configurations
- The Ranger component in EEP 9.2.0 cannot be used in a mixed FIPS configuration (a cluster consisting of FIPS and non-FIPS nodes).
- RAN-279
- If you are upgrading to EEP 9.2.0 or later, you must upgrade both Ranger and Hive
packages together if the Hive plugin is used. If you upgraded only Ranger, you might
encounter the following
error:
Error: Error running query: java.lang.NoSuchMethodError: 'java.lang.String org.apache.hadoop.hive.ql.security.authorization.plugin.HivePrivilegeObject.getOwnerName()' (state=,code=0) - RAN-292
- After upgrading Ranger, the old 3-digit directory might remain. For example, after
upgrading from Ranger version 2.3.0 to version 2.4.0, you might see the
following:
The[mapr@node2 ~]$ ls -l /opt/mapr/ranger/ total 16 drwxr-xr-x 3 mapr mapr 4096 Sep 20 10:25 ranger-2.3.0 drwxr-xr-x 3 mapr mapr 4096 Sep 20 10:23 ranger-2.3.0.300.202307050726 drwxr-xr-x 8 mapr mapr 4096 Sep 20 10:23 ranger-2.4.0 -rw-r--r-- 1 mapr mapr 6 Sep 20 10:24 rangerversionranger-2.3.0is the old directory that was not removed on upgrade. This does not affect anything, and it is safe to remove the directory manually. - RAN-292
- On Debian-based distributions, upgrading Ranger might throw the following
warning:
This issue does affect anything and can safely be ignored.dpkg: warning: unable to delete old directory '<directory>': Directory not empty
Resolved Issues
HMS functionalities are supported in a preview state.