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

New Features and Changes in Cloudera Navigator 2

The following sections describe what’s new and changed in each Cloudera Navigator 2 release.

New Features in Cloudera Navigator 2

The following sections describe what’s new in each Cloudera Navigator 2 release.

What's New in Cloudera Navigator 2.0.5

An issue was fixed. See Issues Fixed in Cloudera Navigator 2.0.5.
  Note: There is no Cloudera Navigator 2.0.4 release.

What's New in Cloudera Navigator 2.0.3

A number of issues have been fixed. See Issues Fixed in Cloudera Navigator 2.0.3.

What's New in Cloudera Navigator 2.0.2

An issue was fixed. See Issues Fixed in Cloudera Navigator 2.0.2.

What's New in Cloudera Navigator 2.0.1

  • Optional masking of personally identifiable information (PII) in query strings that appear in audit events and lineage. Enabled by default.
  • REST API support for registering business metadata for entities before they appear in Navigator.

What's New in Cloudera Navigator 2.0.0

  • Auditing Component
    • Added support for auditing the Sentry service
    • Added support for publishing audit logs to syslog
  • Metadata Component
    • Newly designed Query Builder with faceted filtering
    • Simplified Pig lineage
    • Added support for Sqoop and Oozie lineage
    • Many performance and stability improvements
  • Security - includes Navigator Encrypt and Navigator Key Trustee, formerly known as Gazzang zNcrypt and Gazzang zTrustee. These features provide enterprise-grade encryption and key management. For information on these features, see the Cloudera Security Datasheet and contact your account team.

Changed Features in Cloudera Navigator 2

The following sections describe what’s changed in each Cloudera Navigator 2 release.

What's Changed in Cloudera Navigator 2.0.1

  • Metadata Component
    • The REST API version changed to v2.

What's Changed in Cloudera Navigator 2.0.0

  • Auditing Component
    • Events generated by the solr user are discarded by default.