Table of Contents

Search

  1. Preface
  2. Using Metadata Manager
  3. Viewing Metadata
  4. Searching Metadata
  5. Working with Shortcuts and Folders
  6. Editing Metadata
  7. Working with Data Lineage
  8. Sharing Metadata
  9. Business Glossaries
  10. Using the URL API
  11. Appendix A: Configure the Web Browser
  12. Appendix B: Glossary

Metadata Manager User Guide

Metadata Manager User Guide

Rules and Guidelines for Filtering Objects

Rules and Guidelines for Filtering Objects

Use the following rules and guidelines when you apply filters to a data lineage diagram:
You cannot filter the source object, its parent objects, or its child objects.
For example, if you run data lineage analysis on a relational column, you cannot filter the column or the table that contains the column. If you run data lineage analysis on a relational table, you cannot filter the relational table or any column in the table. You cannot filter synonyms of the table.
Alternatively, you run data lineage analysis on a Cognos query, and then you filter all Cognos queries. Metadata Manager removes all of the Cognos queries except for the query from which you generated the diagram.
You cannot filter non-lineageable objects.
For example, you cannot filter repositories or relational schemas, even though these objects appear in the data lineage diagram.
Filtering an object also filters the upstream or downstream objects that are in the same data path as the filtered object.
For example, you run data lineage analysis from an Oracle view with the following lineage:
ERwin table → Oracle table → Oracle view* → PowerCenter mapping → Microsoft SQL Server table
If you filter the PowerCenter mapping, Metadata Manager removes the PowerCenter mapping and the downstream SQL Server table from the data lineage diagram. If you filter the Oracle table, Metadata Manager removes the Oracle table and the upstream ERwin table from the diagram.
Metadata Manager does not filter upstream or downstream objects that are in the data path of a non-filtered object.
For example, you run data lineage analysis from Oracle table CUSTOMERS with the following lineage:
If you filter the PowerCenter mapping Map_lkp, Metadata Manager removes the mapping but not the downstream EMPLOYEES table. Metadata Manager does not remove the downstream table because it is in the data path of the mapping that is not filtered.
When there is a loop in the data lineage diagram, Metadata Manager filters upstream or downstream objects based on the direction of lineage.
For example, you run data lineage analysis from a PowerCenter mapping with the following lineage:
This mapping writes data back to Oracle table EMP.
If you filter Oracle view V_EMP, Metadata Manager removes Oracle view V_EMP and the upstream link to Oracle table EMP. The data lineage diagram still shows the downstream link to Oracle table EMP as follows:
When you filter one instance of a reusable PowerCenter object, the filter does not affect instances of the object in other containers.
For example, a reusable PowerCenter transformation appears in multiple mappings in a data lineage diagram. When you filter an instance of the transformation in one mapping, Metadata Manager does not filter instances of the transformation in other mappings.

0 COMMENTS

We’d like to hear from you!