Meta Integration® Model Bridge (MIMB)
"Metadata Integration" Solution

MIMB Bridge Documentation

MIMB Import Bridge from Cloudera Navigator

Bridge Specifications

Vendor Cloudera
Tool Name Navigator
Tool Version 2.x
Tool Web Site http://www.cloudera.com/products/cloudera-navigator.html
Supported Methodology [Metadata Management] Multi-Model, Metadata Repository, Data Store (Physical Data Model), ETL (Source and Target Data Stores, Transformation Lineage, Expression Parsing) via REST API

BRIDGE INFORMATION
Import tool: Cloudera Navigator 2.x (http://www.cloudera.com/products/cloudera-navigator.html)
Import interface: [Metadata Management] Multi-Model, Metadata Repository, Data Store (Physical Data Model), ETL (Source and Target Data Stores, Transformation Lineage, Expression Parsing) via REST API from Cloudera Navigator
Import bridge: 'ClouderaNavigator' 10.1.0

BRIDGE DISCLAIMER
This bridge requires internet access to https://repo.maven.apache.org/maven2/ (and exceptionally a few other tool sites)
in order to download the necessary third party software libraries into $HOME/data/download/MIMB/
(such directory can be copied from another MIMB server with internet access).
By running this bridge, you hereby acknowledge responsibility for the license terms and any potential security vulnerabilities from these downloaded third party software libraries.

BRIDGE DOCUMENTATION
Navigator repositories contain the Hadoop data store definitions of HDFS files and HIVE tables, as well as the data flow lineage of operations between them.
Navigator repositories determine such data flow lineage from the execution log of various technologies (HiveQL, Spark, etc) produced by various applications, ingestion framework /ETL /DI jobs.
The purpose of this Navigator import bridge is NOT to extract the data store definitions, instead use the HIVE and HDFS import bridges for that purpose.
However, the purpose of this Navigator import bridge is to extract the data flow lineage (DI processes) between previously harvested HDFS and HIVE data stores.

Navigator repositories can be extremely large as it contains any HDFS/HIVE transactions over multiple years of activities.
Therefore, it is important filter down the scope of a given Navigator import to a precise data flow activity.
- Entities filter allows to define the data flow starting or end entities by location (e.g. files in various directories, and some precise files), and type (e.g. HIVE tables, HDFS files)
- Lineage Direction allows to pick a data flow direction from the above entities (i.e upstream or downstream)
- Operations filter allows to the data flow to some operation types (e.g. HiveQL, Spark) and time range (e.g. last week)

Please refer to the individual parameter's tool tips for more detailed examples.


Bridge Parameters

Parameter Name Description Type Values Default Scope
URL URL of the metadata server.
f.e http://localhost:21000/
STRING     Mandatory
Login Name of the user account used to connect to metadata server STRING   holger_gov  
Password Password for the user account used to connect to metadata server. PASSWORD   holger_gov  
Entities filter Bridge will import and build lineage using start entities(tables, files and directories) set, filtered by this parameter. The query syntax is exactly the same as in Cloudera Navigator search ui.

Some queries examples:
path like data.csv
owner:impala
path like *hdfs://quickstart.cloudera:8020/user/hive/warehouse/customers
path like *dirname* and type:directory

To make import faster, please provide as precise as possible query and check filtered entities count in Navigator ui before import.
STRING     Mandatory
Operations filter Use this parameter to limit imported operations by date or sourceType f.e:
started:[2019-02-25T00:00:000Z TO 2019-02-27T00:00:000Z] and sourceType:impala

*Using of this option will bring additional requests to API server which may slow down the import process
STRING      
Lineage direction Use this parameter to set lineage extract direction ENUMERATED
Both
Upstream
Downstream
BP_LINEAGE_DIRECTION_BOTH  
Kerberos configuration file Path to kerberos krb5 config file (usually krb5.ini or krb5.conf with correct configuration inside)
Example: /etc/krb5/krb5.conf
STRING      
Kerberos login.conf file Path to login.conf with correct keytab file path and principal name. F.e:
client {
com.sun.security.auth.module.Krb5LoginModule required
useKeyTab=true
storeKey=true
keyTab=/path/to/userKeytab
principal='userName';
};
STRING      
Miscellaneous Specify miscellaneous options identified with a -letter and value.

For example, -m 4G -f 100 -j -Dname=value -Xms1G

-m the maximum Java memory size whole number (e.g. -m 4G or -m 2500M ).
-s import system objects that are skipped by default (e.g. -s)
-v set environment variable(s) (e.g. -v var1=value -v var2='value with spaces').
-j the last option that is followed by Java command line options (e.g. -j -Dname=value -Xms1G).
-request.limit 100 - use to specify maximum entities number to fetch per one request
-connection.timeout 20 - use to specify request connection timeout in seconds
-backup.dir C:\test\backupDir - specify directory path to backup atlas api response
-restore.dir C:\test\restoreDir - specify directory path to restore backup data
-threads.count 30 -specify number of threads to use while performing requests to api;
-cs * - create separate connections for all database schemas
-cs c1, c2 - create separate connections for all database schemas of 'c1' and 'c2' connections
-cs app1=c.s1 - create 'app1' connection for the 's1' schema in the 'c' connection
-cd a_con=orig_con:/root/a - create 'a_con' connection for the 'root/a' folder branch in the 'a_con' connection.
-cd hdfs://nameservice2/podium=hdfs://nameservice1/podium
-load.physicals use to enable logical-physical relations import
STRING      

 

Bridge Mapping

Mapping information is not available

Last updated on Wed, 11 Dec 2019 18:39:35

Copyright © Meta Integration Technology, Inc. 1997-2019 All Rights Reserved.

Meta Integration® is a registered trademark of Meta Integration Technology, Inc.
All other trademarks, trade names, service marks, and logos referenced herein belong to their respective companies.