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

MIMB Bridge Documentation

MIMB Import Bridge from JSON File

Bridge Specifications

Vendor ISO
Tool Name JSON (JavaScript Object Notation) File
Tool Version 1.0
Tool Web Site
Supported Methodology [File System] Data Store (NoSQL / Hierarchical, Physical Data Model) via

Import tool: ISO JSON (JavaScript Object Notation) File 1.0 (
Import interface: [File System] Data Store (NoSQL / Hierarchical, Physical Data Model) via from JSON File
Import bridge: 'Json' 10.1.0

IMPORTING METADATA FROM JSON FILES USING NATIVE JAVA API. This bridge loads Json files content and parse loaded documents in order to extract the physical metadata. Please refer to the individual parameter's tool tips for more detailed examples.

Bridge will assign a data type for each JSON attribute according to following samples:
"_id" : { "$oid": "50a9c951300493f64fbffdb6" } STRING (SQL_VARCHAR)
"dateExample" : { "$date" : "2014-01-01T05:00:00.000Z"} DATE_8 (SQL_DATE)
"isoDateExample" : { "$date" : 1491461103897 } DATE_8 (SQL_DATE)
"timestampExample" : { "$timestamp" : { "t" : 1412180887, "i" : 1 } } TIMESTAMP (SQL_TIMESTAMP)
"stringDateExample" : "Thu Apr 06 2017 09:41:51 GMT+0300 (FLE Standard Time)" STRING (SQL_VARCHAR)
"numberLongExample" : { "$numberLong": "7494814965" } LONG_8 (SQL_BIGINT)
"booleanSample" : true BOOLEAN_1 (SQL_BOOLEAN)
"stringSample" : "some text" STRING (SQL_VARCHAR)
"expNumberSample" : 2.99792458e8 DOUBLE_10_5 (SQL_DOUBLE)
"smallNumberSample" : -1 LONG_8 (SQL_BIGINT)
"numberSample" : 3 LONG_8 (SQL_BIGINT)
"floatSample" : 3.141592653589793238462643383279 DOUBLE_10_5 (SQL_DOUBLE)
"rfc7493bignumber" : "9007199254740992" STRING (SQL_VARCHAR)
"expStringSample" : "2.99792458e8" STRING (SQL_VARCHAR)
"arraySample" : [1, 2, 3] array (SQL_ARRAY)
"objectEmptySample" : {} STRING (SQL_VARCHAR)
"nullSample" : null undefined
"nullStringSample" : "null" STRING (SQL_VARCHAR)

Bridge Parameters

Parameter Name Description Type Values Default Scope
File Path to file to import FILE *.*   Mandatory
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 ).
-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).
-hadoop key1=val1;key2=val2 to manualy set hadoop configuration options
-tps 10 maximum threads pool size
-tl 3600s processing time limit in s -seconds m - minutes or h hours;
-fl 1000 processing files count limit;
-delimited.top_rows_skip 1 number of rows to skip while processing csv files
-delimited.extra_separators ~,||,|~ comma separated extra delimiters each of which will be used while processing csv files
-delimited.no_header by default, bridge automatically tries to detect headers while processing csv files(basing on header columns types), use this option to disable headers import(f.e. to hide sensitive data)
-fresh.partition.models - use to import latest modified files when processing partitions defined in Partitioned directories parameter
-subst K: C:/test - use to associate a root path part with a drive or another path. - use to disable dependencies downloading and use only download cache
-prescript [cmd] - runs a script command before bridge execution. Example: -prescript \"script.bat\"
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.
-disable.partitions.autodetection - use this option to disable automatic partitions detection(when "Partition directories" option is empty)


Bridge Mapping

Mapping information is not available

Last updated on Fri, 17 Jan 2020 17:32:42

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.