This is the documentation for Cloudera Navigator 2.0.0.
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.

Lineage does not work when launched on a field

When you launch lineage on a field (Hive column or Pig field, or a Sqoop sub-operation), the UI displays the initial graph properly. However if you expand the parent item (Hive table in case of a Hive column), then things start disappearing from the lineage diagram.

Workaround: None.

From a lineage perspective, Hive views are treated tables

The lineage of the underlying tables does not appear in the lineage view.

Workaround: Launch lineage on the underlying tables directly.

When you specify an end date for the created property, no results are returned.

Workaround: Clear the end date control or specify an end date of TO+*%5D%22%7D.

Navigating back to the parent entity in a Pig lineage diagram sometimes displays the error: Cannot read property 'x' of undefined.

Workaround: None.

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.