Skip to content

You are viewing documentation for Immuta version 2.8.

For the latest version, view our documentation for Immuta SaaS or the latest self-hosted version.

Immuta v2.6.0 Release Notes

Immuta v2.6.0

Immuta version 2.6.0 was released September 3, 2019.

v2.6.0 New Features

Major Features

  • Sensitive Data Detection: Automatic discovery of sensitive entities in your data. This optional setting takes a small sample of data and uses that to tag sensitive entity types in a column, such as name or address. These tags can be managed and used to drive Immuta Global Policies.

  • "Native" Workspace in HDFS. When enabled in equalized projects, this feature creates a directory in HDFS that only project members can access and write/update data to and allows the creation of HIVE and/or Impala tables from the data that they generate in the workspace.

  • Purpose Hierarchies. Previously, purposes had no explicit organizational structure. Now, a Governor can create purposes in a tree structure.

  • Restricted Global Policies. Restricted Global Policies are Global Policies that Data Owners —- who are not Governors —- may build. The application of these policies is restricted to data sources they own.

  • Data access through S3 APIs.

Minor Features

  • REST interface for tagging. Immuta has exposed a standard REST interface that can be implemented that will tag new data sources automatically from customer-specific cataloging systems.

  • REST interface for user attributes. Immuta has exposed a standard REST interface that can be implemented that will add attributes from customer-specific systems to a user whenever they log into Immuta.

  • Webhooks. Webhooks allow people or other systems to get notified when actions happen within Immuta. Every action that currently generates a notification will now also be available as a webhook.

  • ElasticSearch as a data source.

  • Alation as an external catalog provider.

  • Google Catalog as an external catalog provider.

  • The query we send to the remote database now contains a comment saying it was from Immuta and includes a UUID that can be tied to an Immuta audit record.

  • All audited queries include both the query sent to Immuta, as always, and now also include a second entry containing the remote database query sent by Immuta (post policy-enforced).

  • Columns/tables up to 254 characters in length; prior to that only a length of 63 was supported.

  • Easier, GUI-driven, plugin deployment.

  • A new Immuta Report that shows last login for users.

v2.6.0 Major Bug Fixes

  • Changed background jobs from a polling mechanism to a push mechanism so that jobs can be processed faster with less overhead.

  • Data source creation workflow performance improvements for query-backed data source creation.

v2.6.0 Known Bugs

  • Writing ORC in the HDFS workspace and creating a Hive table will not load date fields.

v2.6.0 Deprecation Notices

  • Removed the feature store for blob-based data sources.
  • The Immuta Virtual Filesystem has been deprecated.

v2.6.0 Breaking API Changes

  • A number of optional fields were completely removed from the create data source endpoint and are no longer allowed to be sent.