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

MIMB Bridge Documentation

MIMB Import Bridge from Apache Hadoop HBase NoSQL Database (Java API)

Bridge Specifications

Vendor Apache
Tool Name Hadoop HBase NoSQL Database
Tool Version HBase 2.x
Tool Web Site
Supported Methodology [NoSQL Database] Data Store (NoSQL / Hierarchical, Physical Data Model) via Java API

Tool: Apache / Hadoop HBase NoSQL Database version HBase 2.x via Java API
Metadata: [NoSQL Database] Data Store (NoSQL / Hierarchical, Physical Data Model)
Component: HBase version 11.0.0




Refer to the current general known limitations at or bundled in Documentation/ReadMe/MIMBKnownLimitations.html

Provide a trouble shooting package with:
- the debug log (can be set in the UI or in conf/ with MIR_LOG_LEVEL=6)
- the metadata backup if available (can be set in the Miscellaneous parameter with option -backup)

Bridge Parameters

Parameter Name Description Type Values Default Scope
Hadoop client location Directory containing JAR files neccessary to access HBase via Java API (typically available under /usr/lib/hadoop/client). DIRECTORY   Hadoop/hdfs/usr/lib/hadoop/client Mandatory
HBase configuration directory Directory containing copies of core-site.xml, hdfs-site.xml and hbase-site.xml from remote cluster you are trying to access.

Please make attention that configuration files contains valid from client perspective IP address, Host names etc.
Also make sure that following properties are properly configured:

DIRECTORY     Mandatory
Tables Used as a constraint to import a particular HBase Table by specifying a list of tables separated by a semicolon.

The possible values are:
- empty string
Any tables found with the connection parameters specified will be imported.

- a name or names
Only the name(s) that belong to this table will be imported.

Import column families from 'table1' and 'table2'

Import column families from 'table2' in namespace 'namespace1'

Import column families from all tables with name started with 'ta' in namespace 'namespace1'
Miscellaneous Specify miscellaneous options starting with a dash and optionally followed by parameters, e.g.
-connection.cast MyDatabase1="SQL Server"
Some options can be used multiple times if applicable, e.g.
-connection.rename NewConnection1=OldConnection1 -connection.rename NewConnection2=OldConnection2;
As the list of options can become a long string, it is possible to load it from a file which must be located in ${MODEL_BRIDGE_HOME}\data\MIMB\parameters and have the extension .txt. In such case, all options must be defined within that file as the only value of this parameter, e.g.

-m <Java Memory's maximum size>
1G by default on 64bits JRE or as set in conf/, e.g.
-m 8G
-m 8000M

-j <Java Runtime Environment command line options>
This option must be the last one in the Miscellaneous parameter as all the text after -j is passed "as is" to the JRE, e.g.
-j -Dname=value -Xms1G
The following option must be set when a proxy is used to access internet (this is critical to access (and exceptionally a few other tool sites) in order to download the necessary third party software libraries.
-j -Dhttp.proxyHost= -Dhttp.proxyPort=3128 -Dhttps.proxyHost= -Dhttps.proxyPort=3128 -Dhttp.proxyUser=user -Dhttp.proxyPassword=pass -Dhttps.proxyUser=user -Dhttps.proxyPassword=pass

-jre <Java Runtime Environment full path name>
It can be an absolute path to javaw.exe on Windows or a link/script path on Linux, e.g.
-jre "c:\Program Files\Java\jre1.8.0_211\bin\javaw.exe"

-v <Environment variable value>
None by default, e.g.
-v var1=value1 -v var2="value2 with spaces" <model name>
Override the model name, e.g. "My Model Name"

-prescript <script name>
The script must be located in the bin directory, and have .bat or .sh extension.
The script path must not include any parent directory symbol (..).
The script should return exit code 0 to indicate success, or another value to indicate failure.
For example:
-prescript "script.bat arg1 arg2"

Clears the cache before the import, and therefore will run a full import without incremental harvesting.
Warning: this is a system option managed by the application calling the bridge and should not be set by users.


Bridge Mapping

Mapping information is not available

Last updated on Fri, 25 Sep 2020 17:37:51

Copyright © Meta Integration Technology, Inc. 1997-2020 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.