The earlier metamodel/profile for JSON was too limited and incomplete as it did not model both arrays and structures, and did not capture the root object which could be an array. This situation has been corrected in the latest product. This change has impact in many places both MIMB and MIMM.
In MIMB, JSON is used by almost all bridges except databases.
o File System / Data Lakes
o File System (Delimited, Fixed Width, Excel, XML, JSON, Avro, Parquet, ORC, COBOL Copybook)
o AWS Simple Storage Service (S3) File System
o Azure Data Lake Storage (ADLS) File System
o Azure Blob Storage File System
o Google Cloud Storage (GCS) File System
o Kafka File System
o Swift Object Store File System
o NoSQL databases bvased on JSON
o MongoDB
o Azure Cosmos DB NoSQL Database
o Cassandra
o CouchDB
o ETL/DI/BI bridges reading/writing JSON file based data stores
o Data Mapping Script
o any DI tool supporting hierrachies like Talend DI jobs (many stitched to JSON files)
o Haddop HiveQL
In MIMM, JSON is also used with
o Model Browser
o Data Mapper
o Data Flow
o Configuration / Connection resolutions
o And others.
In order to ensure proper migration and no loss of metadata and no loss of linking (documentation, mappings, stitching/data flow, etc.) this upgrade is performed automatically as part of the database upgrade to this latest version.