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

Known Issues and Workarounds in Cloudera Navigator 2

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

Metadata Component in Cloudera Navigator 1.2 cannot be upgraded to 2.0

Cloudera does not provide an upgrade path from the Navigator Metadata component in Cloudera Navigator 1.2 to the Cloudera Navigator 2.0 release. If you are upgrading from Cloudera Navigator 1.2, you must perform a clean install of Cloudera Navigator 2.0. Therefore, if you have Cloudera Navigator roles from a previous beta release:
  1. Delete the Navigator roles.
  2. Remove the contents of the Navigator Metadata Server storage directory.
  3. Add the Navigator roles according to the process described in Adding and Starting the Navigator Audit Server Role and Adding and Starting the Navigator Metadata Server Role.
  4. Clear the cache of any browser that had previously used the 1.2 release of the Navigator Metadata component. Otherwise, you may observe errors in the Navigator Metadata UI.

Variables in Sqoop queries are not instantiated.

If you have a query that includes a variable, such as A (suppose $A ="EMPID = 123456"), the Sqoop command line will list $A but it will not instantiate the variable.

Workaround: None.

The Hive 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.

The 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.

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.