Known Issues in the Current Release

The following sections describe the current known issues and fixed issues in each Cloudera Navigator release.

Known Issues in the Current Release

— If auditing is enabled, during an upgrade from CM 4.6.3 to 4.7, the Impala service won't start.

Impala auditing requires the Audit Log Directory property to be set, but the upgrade process fails to set the property.

Severity: Low.

Anticipated Resolution: To be fixed in a future release.

Workaround: Do one of the following:
  • Stop the Cloudera Navigator server.
  • Ensure that you have a Cloudera Navigator license and manually set the property to /var/log/impalad/audit.

— Impala auditing does not support filtering during event capture.

Impala auditing does not support filtering during event capture.

Severity: Low

Anticipated Resolution: To be fixed in a future release.

Workaround: None.

— The IP address in a Hue service audit log shows as "unknown".

The IP address in a Hue service audit log shows as "unknown".

Severity: Low

Anticipated Resolution: To be fixed in a future release.

Workaround: None.

— Hive service configuration impact on Hue service auditing

If the audit configuration for a Hive service is changed, Beeswax must be restarted to pick up the change in the Hue service audit log.

Severity: Low

Anticipated Resolution: To be fixed in a future release.

Workaround: None.

— Hive service configuration in Cloudera Navigator

For Hive services, Cloudera Navigator doesn't support the "Shutdown" option for the "Queue Policy" property.

Severity: Low

Anticipated Resolution: To be fixed in a future release.

Workaround: None.