Skip to content

MIMB 11.0.0

Winter 2025 | End Of Life (EOL) 12/31/2025

No longer Supported

Winter 2024 | Deprecated 12/31/2024

Successor major release available.

Winter 2021 | General Availability 01/31/2022

Data / Hierarchical Structures And Arrays (JSON, etc.)

Major improvements of JSON file modeling (metamodel/profile) including new support for root object types, arrays, and more. Consequently any use of JSON in the following import bridges has been redesigned, and therefore requires a full import (i.e. without incremental harvesting):

Data / Complex Types (Arrays, Structures)

New support for complex types (arrays and structures) often on tables implemented/externalized as JSON files, on some import bridges:

Data / Relational Databases (RDBMS, Big Data / Hadoop Hive, etc.)

Data / File Systems (Object Stores, Data Lake, Flat Files / CSV, etc.)

Data / NoSQL Databases (JSON, etc.)

Data Integration (DI/ETL/ELT/Scripts)

  • Metadata Excel Format import bridge (now over 10 years old) does not provide the scalability and capabilities required to support the many new NoSQL and cloud technologies. This bridge is now deprecated in 2022 and will be End Of Life (EOL) unsupported in 2024, as it is replaced by the new Data Mapping Script import bridge below.

  • Data Mapping Script import bridge: new import bridge from data mapping SQL like scripts supporting any source/target technologies (RDBMS, NoSQL, file systems, etc.) to emulate proprietary (or non supported) DI/ETL/ELT/CDC tools and technologies.

    This new Data Mapping Script import is a much more capable and scalable evolution and replacement of the 10 years old Metadata Mapping Excel Format import bridge which has been deprecated in 2022 and will be End Of Life (EOL) unsupported in 2024.

    The new data mapping script format provides a number of advantages over the older metadata Excel format (deprecated) including:

    • The data mapping script format supports a full round trip (export/import) from/to a data mapping, while this is not possible with the older metadata Excel format where the export was more for reporting and the import for bootstrapping.

    • The data mapping script format files are generally much more compact than the very verbose metadata Excel format files based on classifier/table maps and feature/column maps.

    • The data mapping script format is easier to generate from SQL based DI/ETL/ELT/CDC tools.

    • The data mapping script format supports both bulk mappings and query mappings, while the metadata Excel format are quite limited in its handling of bulk mappings.

    • The data mapping script format supports more source and target data store technologies (RDBMS, NoSQL, File Systems) that is supported by the metadata Excel format.

  • Amazon Web Services (AWS) Glue ETL (via Apache Spark) import bridge: major improvements.

  • Databricks Unified Data Services (via Apache Spark) import bridge

  • Microsoft Azure Data Factory import bridge: major improvements.

  • Informatica PowerCenter import bridge: major improvement for fast incremental harvesting (up to 10x faster) based on PowerCenter Repository XML incremental generation and rebuild.

  • Snowflake Database SQL DML (DI/ETL) Script (SnowSQL) import bridge: major improvements to support the ETL aspects like SnowPipe, Stream, Task.

  • Talend Data Integration import bridge: major improvements including support for numerous new data connectors and transformations, as well as new support for internal parameter overwrite to improve lineage.

BUSINESS INTELLIGENCE (BI/OLAP)

Business Application (ERP, etc.)

MIMB Credentials On Cloud Secret Managers

allowing administrators to store bridge credentials (e.g. user, password and private key) in a cloud secret manager, including support for:

Mimb Third-Party Software Updates