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

MIMB Bridge Documentation

MIMB Import Bridge from Positional File

Bridge Specifications

Vendor ISO
Tool Name Positional File
Tool Version N/A
Tool Web Site https://en.wikipedia.org/wiki/Flat-file_database
Supported Methodology [File System] Data Store (Physical Data Model) via TXT File

BRIDGE INFORMATION
Import tool: ISO Positional File N/A (https://en.wikipedia.org/wiki/Flat-file_database)
Import interface: [File System] Data Store (Physical Data Model) via TXT File from Positional File
Import bridge: 'PositionalFile' 10.1.0

BRIDGE DOCUMENTATION
This bridge creates metadata for data files of type Positional File (also known as Fixed Length File).
Such metadata cannot be automatically detected (reverse engineered) by sampling the data files (e.g. customers.dat or even just customers with no extension).
Therefore, this bridge imports a 'Positional File Definition' file which must be with extension .positional_file_definition format file
(e.g. customers.dat.positional_file_definition format file will create the metadata of a file named file customers with the fields defined inside)
This is the equivalent of a RDBMS DDL for positional files. With such a long extension, this data definition file can coexist with the actual data files in the each file system directory containing them.

The 'Positional File Definition' file format is defined as follows:
- Format file must start with the following header:
column name, position, width, data type, comment
- All positions must be unique and greater than or equal to 1.
a,1
b,5
- The file format is invalid when some columns have positions and others don't.
a,1
b,
c,5
- When all columns do not have positions but have widths the application assumes that columns are ordered and calculates positions based on widths.
a,,4 -> a,1,4
b,,25 -> b,5,25
- When the position is present the application uses widths for documentation only.
a,1,4
b,5,25
- Types and comments are used as documentation only.
a,1,4,int
b,5,25,char[25],identifier


Bridge Parameters

Parameter Name Description Type Values Default Scope
File The bridge uses the positional_file_definition file as input. FILE *.positional_file_definition   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.
-skip.download - 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)
STRING      

 

Bridge Mapping

Mapping information is not available

Last updated on Tue, 10 Dec 2019 17:32:54

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.