Metadata Manager
This section describes changes to Metadata Manager in version 10.1.1.
Cloudera Navigator Resources
Effective in version 10.1.1, Cloudera Navigator resources have the following behavior changes:
- Incremental loading changes
Incremental loading for Cloudera Navigator resources is disabled by default. Previously, incremental loading was enabled by default.
When incremental loading is enabled, Metadata Manager performs a full metadata load when the Cloudera administrator invokes a purge operation in Cloudera Navigator after the last successful metadata load.
Additionally, there are new guidelines that explain when you might want to disable incremental loading.
- Search query changes
- You can use the search query to exclude entity types besides HDFS entities from the metadata load. For example, you can use the search query to exclude YARN or Oozie job executions.
- Data lineage changes
To reduce complexity of the data lineage diagram, Metadata Manager has the following changes:
- - Metadata Manager no longer displays data lineage for Hive query template parts. You can run data lineage analysis on Hive query templates instead.
- - For partitioned Hive tables, Metadata Manager displays data lineage links between each column in the table and the parent directory that contains the related HDFS entities. Previously, Metadata Manager displayed a data lineage link between each column and each related HDFS entity.
For more information about Cloudera Navigator resources, see the "Database Management Resources" chapter in the Informatica 10.1.1 Metadata Manager Administrator Guide.
Netezza Resources
Effective in version 10.1.1, Metadata Manager supports multiple schemas for Netezza resources.
Netezza resources have the following behavior changes:
- •When you create or edit a Netezza resource, you select the schemas from which to extract metadata. You can select one or multiple schemas.
- •Metadata Manager organizes Netezza objects in the metadata catalog by schema. The database does not appear in the metadata catalog.
- •When you configure connection assignments to Netezza, you select the schema to which you want to assign the connection.
Because of these changes, Netezza resources behave like other types of relational resources.
Previously, when you created or edited a Netezza resource, you could not select the schemas from which to extract metadata. If you created a resource from a Netezza database that included multiple schemas, Metadata Manager ignored the schema information. Metadata Manager organized Netezza objects in the metadata catalog by database. When you configured connection assignments to Netezza, you selected the database to which to assign the connection.
For more information about Netezza resources, see the "Database Management Resources" chapter in the Informatica 10.1.1 Metadata Manager Administrator Guide.