Bridge Specifications
| Vendor | |
| Tool Name | Cloud Data Fusion |
| Tool Version | Current |
| Tool Web Site | https://cloud.google.com/data-fusion |
| Supported Methodology | [Data Integration] Multi-Model, Data Store (Physical Data Model) via REST API |
SPECIFICATIONS
Tool: Google / Cloud Data Fusion version Current via REST API
See https://cloud.google.com/data-fusion
Metadata: [Data Integration] Multi-Model, Data Store (Physical Data Model)
Component: DataplexUniversalCatalog version 12.0.0
OVERVIEW
The bridge is designed to import Dataplex Universal Catalog Lineage entities via the REST API.
The bridge supports two authentication modes: a ready-made 'Access Token' and the 'Service Account ID/Private Key File'
method. Please refer to the description of the 'Access Token' and 'Service Account ID/Private Key File' parameters
for full details.
The bridge provides time-based filtering capabilities for Process Runs, offering two distinct methods:
- Time Interval: This option is simple to use but lacks second-level precision.
- Time Interval Start/Time Interval End: This allows you to specify an exact time range, but its values must be provided in the correct format.
Priority and Usage: The Time Interval Start/Time Interval End parameters take precedence over Time Interval. To utilize the simpler Time Interval option, you must leave both the Start and End parameters empty.
Important Note: These time intervals apply only to Process Runs, not to the parent Processes themselves. Please refer to the parameter descriptions for Time Interval and Time Interval Start/Time Interval End for full details.
The bridge supports the full range of 'Process Types' defined by the Lineage API: https://docs.cloud.google.com/dataplex/docs/reference/data-lineage/rest/v1/projects.locations.processes#SourceType
Use the 'Process type' parameter to filter for the processes you are interested in
See the 'Process type' parameter description for full details.
The 'Process name' parameter enables users to search for and select desired processes.
Dependency: The selection set available in the 'Process name' parameter is constrained by the value supplied to
the 'Process type' parameter, only displaying processes that match the specified type.
You may use the 'Run' paramater to browse and choose the Process Runs you are interested in.
Important Note: The browser of parameter 'Run' respects the 'Process name' parameter and choose the runs
which belong to the specified process.
The 'Source' and 'Destination' parameters are used to refine the selection of Processes and Runs based on the
data stores they involve.
Dependency: The options available in the 'Source' and 'Destination' parameters are constrained by the current
selections in the 'Process Type,' 'Process Name,' and 'Run' fields, ensuring only relevant stores are displayed.
REQUIREMENTS
See the PERMISSIONS section below.
PERMISSIONS
You should have the following permissions:
- datalineage.processes.list
- datalineage.processes.get
- datalineage.runs.get
- datalineage.runs.list
- datalineage.events.list
- datalineage.events.get
to access data lineage.
LIMITATIONS
Refer to the current general known limitations at https://metaintegration.com/Products/MIMB/Help/#!Documents/mimbknownlimitations.html
The Google Cloud REST API does not currently support Column-Level Lineage. Consequently, the bridge is unable \
to import the column and feature maps between entities. According to Google's announcement, the necessary update
is expected to be released in Q1 2026
SUPPORT
Provide a troubleshooting package with:
- the debug log (can be set in the UI or in conf/conf.properties with MIR_LOG_LEVEL=6)
- the metadata backup if available (can be set in the Miscellaneous parameter with -backup option, although this common option is not implemented on all bridges for technical reasons).
Bridge Parameters
| Parameter Name | Description | Type | Values | Default | Scope | |||||||||||
| Project | Mandatory parameter: The unique identifier of the project which contains the Dataplex Universal Catalog instance. | STRING | Mandatory | |||||||||||||
| Location | The Google Cloud region where the lineage metadata is stored and managed. | STRING | Mandatory | |||||||||||||
| Access Token | The 'Access Token'' is a crucial security credential used to authenticate and authorize REST requests. The 'Access token' parameter overrides the 'Service Account ID'. Leave this parameter empty to use the 'Service Account ID' The 'Access Token'' could be retrivied by "gclod" cli command: "gcloud auth print-access-token". https://docs.cloud.google.com/docs/authentication/rest#user-creds |
PASSWORD | ||||||||||||||
| Service Account ID | The Service account which would be used to access Dataplex lineage. The account should have permissions: 'Data Lineage Viewer' | STRING | ||||||||||||||
| Private Key File | Content of the JSON private key file for the Service Account ID | PASSWORD | ||||||||||||||
| Time Interval | The time period of interest. If specified the bridge selects the Runs whose execution interval overlap with this period. |
ENUMERATED |
|
Any | ||||||||||||
| Time Interval Start | The start of the time period of interest. If specified, the bridge selects only the Runs whose execution intervals occur after this timestamp. Left this parameter empty to allow any time. The value should be specified in Standard Format, known as ISO 8601, is the global standard for exchanging date and time information. It follows the pattern: YYYY-MM-DD + T (time separator) + hh:mm:ss.sss + Z (time zone indicator). E.g.:'2025-11-26T23:18:21.526Z'' |
STRING | ||||||||||||||
| Time Interval End | The end of the time period of interest. If specified, the bridge selects only the Runs whose execution intervals occur before this timestamp. Left this parameter empty to allow any time. The value should be specified in Standard Format, known as ISO 8601, is the global standard for exchanging date and time information. It follows the pattern: YYYY-MM-DD + T (time separator) + hh:mm:ss.sss + Z (time zone indicator). E.g.:'2025-11-26T23:18:21.526Z'' |
STRING | ||||||||||||||
| Process type | The enumeration parameter with supported options: 'All' 'BigQuery' 'Data Fusion' 'Data Flow' 'Composer' 'Looker Studio' 'Dataproc' 'Vertex AI' 'A custom source' 'Source is Unspecified' 'Others' |
ENUMERATED |
|
All | ||||||||||||
| Process name | The browsable parameter which specifies the name of process which responsible for generating the lineage data. Left this parameter empty to include all processes |
REPOSITORY_SUBSET | ||||||||||||||
| Run | The browsable parameter which specifies the name of run which responsible for generating the lineage data. |
REPOSITORY_SUBSET | ||||||||||||||
| Source | Fully qualified name case-sensitive resource identifiers that you want use as a source. Wildcard character '*' could be used. Left this parameter empty to include all tables. Predefined formats for Google Cloud resources described at: Fully qualified names | Dataplex Universal Catalog | Google Cloud - Example: "bigquery:my-project.My_Dataset.My_Source_Table" - Specified exact one table 'My_Source_Table' in Bigquery dataset 'My_Dataset' "bigquery:my-project.My_Dataset." - Specified all tables in Bigquery dataset 'My_Dataset' |
REPOSITORY_SUBSET | ||||||||||||||
| Destination | Fully qualified name case-sensitive resource identifiers that you want use as a destination. Wildcard character '' could be used. Left this parameter emty to include all tables. Predefined formats for Google Cloud resources described at: Fully qualified names | Dataplex Universal Catalog | Google Cloud - Example: "bigquery:my-project.My_Dataset.My_Destination_Table" - Specified exact one table 'My_Destination_Table' in Bigquery dataset 'My_Dataset' "bigquery:my-project.My_Dataset." - Specified all tables in Bigquery dataset 'My_Dataset' |
REPOSITORY_SUBSET | ||||||||||||||
| Miscellaneous | INTRODUCTION Specify miscellaneous options starting with a dash and optionally followed by parameters, e.g. -connection.cast MyDatabase1="MICROSOFT 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. ETL/Miscellaneous.txt JAVA ENVIRONMENT OPTIONS -java.memory <Java Memory's maximum size> (previously -m) 1G by default on 64bits JRE or as set in conf/conf.properties, e.g. -java.memory 8G -java.memory 8000M -java.parameters <Java Runtime Environment command line options> (previously -j) This option must be the last one in the Miscellaneous parameter as all the text after -java.parameters is passed "as is" to the JRE, e.g. -java.parameters -Dname=value -Xms1G The following option must be set when a proxy is used to access internet (this is critical to access https://repo.maven.apache.org/maven2/ and exceptionally a few other tool sites) in order to download the necessary third-party software libraries. Note: The majority of proxies are concerned with encrypting (HTTPS) the outside (of the company) traffic and trust the inside traffic that can access proxy over HTTP. In this case, an HTTPS request reaches the proxy over HTTP where the proxy HTTPS-encrypts it. -java.parameters -java.parameters -Dhttp.proxyHost=127.0.0.1 -Dhttp.proxyPort=3128 -Dhttp.proxyUser=user -Dhttp.proxyPassword=pass MODEL IMPORT OPTIONS -model.name <model name> Override the model name, e.g. -model.name "My Model Name" -prescript <script name> This option allows running a script before the bridge execution. The script must be located in the bin directory (or as specified with M_SCRIPT_PATH in conf/conf.properties), 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" -postscript <script name> This option allows running a script after successful execution of the bridge. The script must be located in the bin directory (or as specified with M_SCRIPT_PATH in conf/conf.properties), 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: -postscript "script.bat arg1 arg2" -cache.clear Clears the cache before the import, and therefore will run a full import without incremental harvesting. If the model was not changed and the -cache.clear parameter is not used (incremental harvesting), then a new version will not be created. If the model was not changed and the -cache.clear parameter is set (full source import instead of incremental), then a new version will be created. -backup <directory> Allows to save the input metadata for further troubleshooting. The provided <directory> must be empty. -restore <directory> Specify the backup <directory> to be restored. DATA CONNECTION OPTIONS Data Connections are produced by the import bridges typically from ETL/DI and BI tools to refer to the source and target data stores they use. These data connections are then used by metadata management tools to connect them (metadata stitching) to their actual data stores (e.g. databases, file system, etc.) in order to produce the full end to end data flow lineage and impact analysis. The name of each data connection is unique by import model. The data connection names used within DI/BI design tools are used when possible, otherwise connection names are generated to be short but meaningful such as the database / schema name, the file system path, or Uniform Resource Identifier (URI). The following option allows to manipulate connections. These options replaces the legacy options -c, -cd, and -cs. -connection.cast ConnectionName=ConnectionType Casts a generic database connection (e.g. ODBC/JDBC) to a precise database type (e.g. ORACLE) for SQL Parsing, e.g. -connection.cast "My Database"="MICROSOFT SQL SERVER". The list of supported data store connection types includes: ACCESS APACHE CASSANDRA DB2/UDB DENODO GOOGLE BIGQUERY HIVE MYSQL NETEZZA ORACLE POSTGRESQL PRESTO REDSHIFT SALESFORCE SAP HANA SNOWFLAKE MICROSOFT SQL AZURE MICROSOFT SQL SERVER SYBASE SQL SERVER SYBASE AS ENTERPRISE TERADATA VECTORWISE HP VERTICA -connection.rename OldConnection=NewConnection Renames an existing connection to a new name, e.g. -connection.rename OldConnectionName=NewConnectionName Multiple existing database connections can be renamed and merged into one new database connection, e.g. -connection.rename MySchema1=MyDatabase -connection.rename MySchema2=MyDatabase -connection.split oldConnection.Schema1=newConnection Splits a database connection into one or multiple database connections. A single database connection can be split into one connection per schema, e.g. -connection.split MyDatabase All database connections can be split into one connection per schema, e.g. -connection.split * A database connection can be explicitly split creating a new database connection by appending a schema name to a database, e.g. -connection.split MyDatabase.schema1=MySchema1 -connection.map SourcePath=DestinationPath Maps a source path to destination path. This is useful for file system connections when different paths points to the same object (directory or file). On Hadoop, a process can write into a CSV file specified with the HDFS full path, but another process reads from a Hive table implemented (external) by the same file specified using a relative path with default file name and extension, e.g. -connection.map /user1/folder=hdfs://host:8020/users/user1/folder/file.csv On Linux, a given directory (or file) like /data can be referred to by multiple symbolic links like /users/john and /users/paul, e.g. -connection.map /data=/users/John -connection.map /data=/users/paul On Windows, a given directory like C:\data can be referred to by multiple network drives like M: and N:, e.g. -connection.map C:\data=M:\ -connection.map C:\data=N:\ -connection.casesensitive ConnectionName... Overrides the default case insensitive matching rules for the object identifiers inside the specified connection, provided the detected type of the data store by itself supports this configuration (e.g. Microsoft SQL Server, MySql etc.), e.g. -connection.casesensitive "My Database" -connection.caseinsensitive ConnectionName... Overrides the default case sensitive matching rules for the object identifiers inside the specified connection, provided the detected type of the data store by itself supports this configuration (e.g. Microsoft SQL Server, MySql etc.), e.g. -connection.caseinsensitive "My Database" -connection.level AggregationLevel Specifies the aggregation level for the external connections, e.g.-connection.level catalog The list of the supported values: server catalog schema (default) ETL OPTIONS These options are available on all ETL/DI tools and scripting import bridges in order to: - Process all SQL parsing - Build runtime models from design models and runtime variables - Calculate runtime summary lineage -etl.summary.add.ultimate (previously -ppus) Adds the ultimate runtime lineage summary (may generate a very large model). -etl.summary.only.ultimate (previously -ppsp) Only produces the ultimate runtime lineage summary (may generate a very large model). -etl.connections.add.internal.design (previously -pppd) Adds the internal ETL design data connectors (needed for ETL conversion). -etl.connections.remove.input (previously -ri) Removes all input (source) data connections (to reduce the size of the generated model). -etl.transformations.enable.xml This option enables the parsing and support of XML transformations in DI/ETL import bridges such as Informatica PowerCenter, Informatica Developer, Microsoft SSIS, IBM DataStage, and Talend Data Integration. In case of Informatica, such XML transformations corresponds to the following PowerCenter features https://docs.informatica.com/data-integration/powercenter/10-5/xml-guide/midstream-xml-transformations.html https://docs.informatica.com/data-integration/powercenter/10-5/xml-guide/xml-source-qualifier-transformation.html Note that this option may significantly slow down the import. -cache.clear Clears the cache before the import, and therefore will run a full import without incremental harvesting. |
STRING |
Bridge Mapping
Mapping information is not available