Preface
Using Metadata Manager
- Using Metadata Manager Overview
  - Resource Types
- Metadata Manager Architecture
- Metadata Integration Process
- Working with Metadata Manager
- Metadata Manager Interface
  - Load Tab
  - Permissions Tab
Configuring Metadata Manager
- Configuring Metadata Manager Overview
- Step 1. Create and Configure the Metadata Manager Service
- Step 2. Install the Metadata Manager Agent
Application Resources
- SAP R/3 Resource Overview
- Configuring SAP R/3
- Creating an SAP R/3 Resource
  - SAP R/3 Configuration Properties
- Configuring the Component Inclusion List
- Reference
Business Glossary Resources
- Business Glossary Resources Overview
- Application Services Verification
- Creating a Business Glossary Resource
  - Business Glossary Connection Properties
- Business Glossary Objects Extracted
- Business Glossary Objects Not Extracted
Business Intelligence Resources
- Business Objects
- Cognos
- Microsoft Analysis and Reporting Services
- Microstrategy
- Oracle Business Intelligence Enterprise Edition
- Tableau
- Incremental Metadata Load
- Adding or Removing Metadata Files for a Resource
Custom Resources
- Configuring Custom Metadata Sources
- Creating a Custom Resource
- Configuring the Template Name
- Adding or Removing Metadata Files for a Resource
Data Integration Resources
- Informatica Platform Resources
- Microsoft SQL Server Integration Services Resources
- PowerCenter Resources
Data Modeling Resources
- Embarcadero ERStudio
- ERwin
- SAP PowerDesigner
- Adding or Removing Metadata Files for a Resource
- Reference for Data Modeling Resources
Database Management Resources
- Cloudera Navigator
- IBM DB2 for LUW
- IBM Db2 for z/OS
- IBM Informix
- JDBC
- Microsoft SQL Server
- Netezza
- Oracle
- Sybase ASE
- Teradata
- Configuring the Schema Inclusion List
- Data Lineage for Database Management Resources
  - Tables in Join Statements
  - SQL Inline Views
Universal Resources
- Universal Resources Overview
- Available Metadata Sources
- XConnect Creation
- Resource Creation
  - Step 1. Configure the Metadata Source
  - Step 2. Create the Resource
    - Metadata Extraction from a Source File
Managing Resources
- Managing Resources Overview
- Configure Connection Assignments
- Upload Rule Sets
  - Linking Rules Files
  - Uploading a Rule Set
- Purging Metadata
- Refreshing the Resources Panel
- Updating the Search Index
- Customizing the List of Words to Ignore in Searches
Loading and Monitoring Resources
- Loading and Monitoring Resources Overview
- Loading Resources
- Linking Objects Across Resources
- Monitoring Resources
- Logs and Log Files
- Troubleshooting Resource Loads
- Scheduling Resource Loads
Managing Permissions
- Managing Permissions Overview
- Configuring Permissions for Users and Groups
- Configuring Permissions on the Metadata Catalog
Resource Migration
- Resource Migration Overview
- Resource Migration Steps
- Step 1. Copy the Plug-in for a Universal XConnect
- Step 2. Migrate the Model
  - Exporting a Packaged or Universal Model
  - Importing a Packaged or Universal Model
- Step 3. Migrate the Resource Configuration
  - Exporting a Resource Configuration
  - Importing a Resource Configuration
- Step 4. Load the Resource
- Step 5. Migrate Resource Metadata
  - Exporting Resource Metadata
  - Importing Resource Metadata
Repository Migration
- Repository Migration Overview
- Migrating the Repository when Domain Names and Encryption Keys are the Same
- Migrating the Repository when Domain Names or Encryption Keys Differ
Appendix A: Metadata Manager Login
- Metadata Manager Login Overview
- Cookies
- Logging in to Metadata Manager
- Changing a Password
Appendix B: Metadata Manager Properties Files
- imm.properties
  - Metadata Manager Application Properties
  - Data Lineage Properties
- searchpriorities.xml
  - Search Result Configuration
  - Sample searchpriorities.xml File
Appendix C: Resource Configuration Files
- Resource Configuration Files Overview
- Resource Configuration File Format
- Passwords in Resource Configuration Files
- Secure JDBC Parameters in Resource Configuration Files
- Sample Resource Configuration File
Appendix D: Glossary
- Glossary of Terms

Metadata Manager Administrator Guide

10.5.2
- 10.5.6
- 10.5.5
- 10.5.3
- 10.5.1
- 10.5
- 10.4.1
- 10.4.0

Back Next

How Metadata Manager Displays Entity Relationships

The metadata component of Cloudera Navigator displays different types of entity relationships in data lineage diagrams. Metadata Manager does not display all of these relationships in data lineage diagrams. Metadata Manager displays entity relationships differently based on the relationship type.

Metadata Manager displays the following Cloudera entity relationship types in different ways:

Data flow relationships: A data flow relationship defines how data flows between metadata objects. For example, a Hive query uses an INSERT OVERWRITE TABLE statement to load data into a Hive table. Because data flows from the Hive query to the Hive table, a data flow relationship exists between the query and the table.

Cloudera Navigator displays data flow relationships in data lineage diagrams as solid arrows. Metadata Manager displays data flow relationships as lineage links in data lineage diagrams and as related catalog objects in the metadata catalog.
Logical-physical relationships: A logical-physical relationship indicates that a logical object is based on an actual, physical entity. For example, a Hive table is a logical view of a physical HDFS entity.

Cloudera Navigator displays logical-physical relationships in data lineage diagrams as solid lines without arrow heads. Metadata Manager displays logical-physical relationships as related catalog objects in the metadata catalog.
Instance relationships: An instance relationship defines a single occurrence of an operation. For example, an Oozie job execution is an instance of an Oozie job template.

Cloudera Navigator displays instance relationships for query and job templates on a separate tab in the data lineage diagram. Metadata Manager displays instance relationships as related catalog objects in the metadata catalog.
Control flow relationships: A control flow relationship places constraints or conditions on the flow of data. For example, a Hive query can contain constraints in the WHERE clause. Or, the JOIN clause in a Hive query might include a Hive table from which no data is extracted.

Cloudera Navigator displays control flow relationships in data lineage diagrams as dashed lines. Metadata Manager ignores control flow relationships.

For example, your Hadoop cluster contains a Hive products table with price and cost columns. It also contains a Hive query template with the following query:

SELECT AVG(price - cost) AS profit FROM products JOIN order_details ON (order_details.prod_id = products.prod_id) JOIN orders ON (order_details.order_id = orders.order_id) WHERE YEAR(order_date) = 2014 AND MONTH(order_date) = 12 AND price >= 500

In this query, the SELECT statement indicates that data flows from the products table to the Hive query. The JOIN clauses include two Hive tables, order_details and orders, from which no data is extracted.

Cloudera Navigator shows data flow from the products table to the Hive query. It also shows control flow relationships between the order_details table and the Hive query and between the orders table and the Hive query.

Metadata Manager also shows data flow from the products table to the Hive query. However, Metadata Manager does not show any relationship between the order_details or orders tables and the Hive query.

To view the relationship type between entities in a Cloudera Navigator data lineage diagram, download and view the lineage JSON file.

Rename Saved Search

Table of Contents

Metadata Manager Administrator Guide

Metadata Manager Administrator Guide

How Metadata Manager Displays Entity Relationships

How Metadata Manager Displays Entity Relationships