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

MIMB Bridge Documentation

MIMB Import Bridge from Apache Atlas

Bridge Specifications

Vendor Apache
Tool Name Atlas
Tool Version API 2.0
Tool Web Site http://atlas.apache.org/
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: Apache Atlas API 2.0 (http://atlas.apache.org/)
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 Apache Atlas
Import bridge: 'ApacheAtlas' 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
Atlas repositories contain the Hadoop data store definitions of HDFS files and HIVE tables, as well as the data flow lineage of operations between them.
Atlas repositories determine such data flow lineage from the execution log of various technologies (Map/Reduce, Pig, Impala, etc) produced by various applications, ingestion framework /ETL /DI jobs.
The purpose of this Atlas 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 Atlas import bridge is to extract the data flow lineage (DI processes) between previously imported HDFS and HIVE data stores.
Note that the dedicated HiveQL or Spark import bridges should be preferred in order to get better detailed feature/column level lineage with correlation to the original scripts.

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  
Processes You can limited process types the bridge should import using the 'Processes' bridge parameter.
Here is the list of supported process types:
-hive
-sqoop
-storm
-falcon

The bridge import all supported process types when the parameter value is empty (default).
You can type 'none' parameter value to not import any processes.
f.e.: hive, sqoop
STRING      
Load columns Set this option to 'true' if You want to load all columns to assets that take part in processes lineage. BOOLEAN
False
True
True  
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
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.