Reply
Highlighted
Cloudera Employee
Posts: 15
Registered: ‎08-29-2016

[ANNOUNCE] Cloudera Enterprise 5.9.1 Released

Dear CDH, Cloudera Manager, and Cloudera Navigator users,

 

We are pleased to announce the release of Cloudera Enterprise 5.9.1 (CDH 5.9.1, and Cloudera Manager 5.9.1, and Cloudera Navigator 2.8.1).

 

This release fixes key bugs and includes the following:

 

  • CDH fixes for the following issues:

 

    • HADOOP-12483 - Maintain wrapped SASL ordering for postponed IPC responses
    • HADOOP-13353 - LdapGroupsMapping getPassward should not return null when IOException throws
    • HBASE-15430 - Failed taking snapshot - Manifest proto-message too large
    • HBASE-15856 - Do not cache unresolved addresses for connections
    • HDFS-6962 - ACLs inheritance conflict with umaskmode
    • HDFS-8269 - getBlockLocations() does not resolve the .reserved path and generates incorrect edit logs when updating the atime
    • HUE-5028 - Share Oozie workflow with modify permission; however, the user can't edit the shared WF
    • HUE-5163 - Speed up initial page rendering
    • HUE-5041 - Hue export large file to HDFS doesn't work on non-default database
    • HUE-4941 - Content Security Policy directive blocks an image when navigating on marker map
    • HUE-4631 - DB transaction failing because of atomic block on home page
    • HUE- 5218 - Validate dashboard sharing works
    • IMPALA-4076 - Fix runtime filter sort compare method
    • IMPALA-4120 - Incorrect results with LEAD() analytic function
    • IMPALA-4135 - Thrift threaded server times out connections during high load
    • IMPALA-4170 - Fix identifier quoting in COMPUTE INCREMENTAL STATS
    • IMPALA-4237 - Fix materialization of 4-byte decimals in data source scan node
    • IMPALA-4246 - SleepForMs() utility function has undefined behavior for > 1s
    • IMPALA-4336 - Cast exprs after unnesting union operands
    • IMPALA-4387 - Validate decimal type in Avro file schema
    • IMPALA-4423 - Correct but conservative implementation of Subquery.equals().
    • SENTRY-1313 - Database prefix is not honoured when executing grant statement
    • SQOOP-2983 - OraOop export has degraded performance with wide tables
    • YARN-3601 - Fix UT TestRMFailover.testRMWebAppRedirect



For a full list of upstream JIRAs fixed in CDH 5.9.1, see the issues fixed section of the Release Notes.

 

  • Cloudera Manager fixes for the following issues:

 

    • Cloudera Manager blocks from HS2 enabling both LDAP and Kerberos authorization: HS2 now supports LDAP and Kerberos authentication on the same instance for CDH 5.7.0 or higher. Previously, this was considered an error.
    • Support non-public schemas: Cloudera Manager used to work with only the public schema in Postgresql. With this change, Cloudera Manager now supports custom schema names. Cloudera Manager relies on the schema search path in postgresql, which can be set for a user, database, etc: See https://www.postgresql.org/docs/current/static/ddl-schemas.html
    • Alert Publisher throws "unsigned 32bit value" error after long uptime: Fixes an issue where the Alert Publisher throws "unsigned 32bit value" error after long uptime. TimeTick is an extension of UnsignedInteger32 type. TimeTick represents time in 1/100 seconds. Its value range is 0 to 4294967295. Activity Monitor's uptime is a Java long type that can exceed the range of TimeTicks. Before this fix, long uptime could cause the Alert Publisher to throw the "unsigned 32bit value" error.

 

For a full list of issues fixed in Cloudera Manager 5.9.1, see the issues fixed section of the Release Notes.

 

  • Cloudera Navigator fixes for the following issues:

 

    • Some APIs return incorrect error: In some cases, when a user performs an action with managed metadata that is not permitted because of the user role, Navigator issues an Access Denied error message (500) instead of the expected Forbidden error (403).
    • Resource path filtering does not working in audit event filter
    • Lineage options and search items are missing: In the Safari browser, lineage options and lineage search could be empty in certain cases.
    • Navigator logout link does not work when SAML is enabled: When SAML is enabled, clicking on the Logout link in Navigator executes only a local browser logout, without terminating the SAML session. As a result, after logging out, a user can log in again from the login page without providing credentials.


For a full list of issues fixed in Cloudera Navigator 2.8.1, see the issues fixed section of the Release Notes.

 

We look forward to you trying it, using the information below:

 

 

As always, we are happy to hear your feedback. Please send your comments and suggestions to the user group or through our community forums. You can also file bugs through our external JIRA projects on issues.cloudera.org.

 

Announcements
Unanswered Topics
No posts to display.