This is the documentation for Cloudera Navigator 1.2.0.
Documentation for other versions is available at Cloudera Documentation.

Known Issues and Workarounds in Cloudera Navigator 1

The following sections describe the current known issues in Cloudera Navigator 1.

Hive operation extractor fails if entities don't exist.

If a Hive query is executed and the tables/views/columns etc. used in the query are deleted before the query is captured by Navigator; then Navigator will not be able to parse the query and will not capture any information for that query.

Workaround: None.

Hive extractor does not handle all Hive statements.

The Hive extractor does not handle the following cases:
  • Table generating functions
  • Lateral views
  • Transform clauses
  • Regular expression in select clause
If a query involves any of the above; lineage will not be complete for that Hive query.

Workaround: None.

The last accessed time for Hive table is incorrect.

Workaround: None.

Pig job that has relations with self is unreadable in lineage view.

The Metadata UI currently does not handle situation where there is a data-flow relation between elements that are also related via parent-child relation.

Workaround: None.

If auditing is enabled, during an upgrade from Cloudera Manager 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.

Workaround: Do one of the following:
  • Stop the Cloudera Navigator Audit 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

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

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

Workaround: None.

Hive service configuration in auditing component.

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

Severity: Low

Workaround: None.