Technical Documentation : Connectors : Adding a Matillion DPC Connection
Was this helpful?
Adding a Matillion DPC Connection
Prerequisites
  • A user with sufficient permissions is required to establish a connection with Matillion DPC.
Note: You can find a link to the configuration template in Zeenea Connector Downloads.
Supported Versions
The Matillion DPC module is compatible with the online version of the product.
Installing the Plugin
The Matillion DPC plugin can be downloaded here: Zeenea Connector Downloads
For more information on how to install a plugin, please refer to the following article: Installing and Configuring Connectors as a Plugin.
Declaring the Connection
Creating and configuring connectors is done through a dedicated configuration file located in the /connections folder of the relevant scanner. The scanner frequently checks for any change and resynchronises automatically.
In order to establish a connection with a Matillion DPC instance, the following parameters in the dedicated file are required:
Changes in version 4.1.0
Parameter
Expected value
name
The name that will be displayed to catalog users for this connection.
code
The unique identifier of the connection on the Zeenea platform. Once registered on the platform, this code must not be modified or the connection will be considered as new and the old one removed from the scanner.
connector_id
The type of connector to be used for the connection. Here, the value must be matillion-dpc and this value must not be modified.
connection.path
The root path of Matillion files
default.warehouse
Replace the default value [Environment Default] for the parameter warehouse for every component
default.database
Replace the default value [Environment Default] for the parameter database for every component
default.schema
Replace the default value [Environment Default] for the parameter schema for every component
Changes in version 5.1.0
The connector accepts 2 inputs: Git or a folder in which you can store your Matillion files. At least one of the two must be configured. By default, the Git configuration is selected (if it fails, it falls back to connection.path).
To configure Git, you need to provide credentials and specify the location of your repository.
You must provide at least one of the following to authenticate:
  • A Git token (connection.git.token)
  • Both a Git username (connection.git.username) AND a Git password (connection.git.password)
Parameter
Expected value
connection.path
Path to file or folder containing description files.
This value is mandatory if no git repository is declared.
If a git repository is declared, the value can be null or a path relative to the repository root.
connection.git.repository
Git repository URL. Optional, use connection.path instead.
URL of the git repository where to read the files.
Example: https://github.com/acme/bigproject
connection.git.branch
Git branch to use. Optional.
Branch to clone. By default, HEAD is used.
Example: https://github.com/acme/bigproject
connection.git.token
Git token. Optional.
Authentication Token. Replaces the usage of the username/password parameters.
connection.git.username
Git username. Optional.
Git user name. Requires password. Replaces the usage of token parameter.
connection.git.password
Git username. Optional.
Git user password. Requires username. Replaces the usage of token parameter.
connection.git.workdir
Local working folder where the git repository will be cloned. Optional. Default: root directory.
connection.git.cleandir
Boolean (true/false) indicating whether the working folder should be deleted after processing. If deleted, the repository will be cloned at each operation, otherwise only an update will be performed. Default value: false
environment-variable
Replace environment variable starting with ${ and ending with }
Configuration example:
environment-variables = {
"V_REPLICA_TABLE_NAME" : "album"
}
User Permissions
In order to collect metadata, the running user's permissions must allow them to access and read folders and files that need cataloging.
Data Extraction
The Matillion DPC connector feeds Zeenea Database with Data Processes. Like other Data Process connectors, it has a single job "synchronize" that discovers all items of interest and creates or updates their documentation in the catalog. Matillion items of interest are Jobs. So, for each Jobs in Matillion DPC, a Data Process should be created in Zeenea.
Synchronization
This connector will harvest all transformation processes identified in the Matillion DPC instance, and automatically represent them in Zeenea.
Lineage
The Matillion DPC connector is able to retrieve the lineage with:
  • Matillion DPC for Redshift
  • Matillion DPC for Snowflake
  • Matillion DPC for Oracle
  • Matillion DPC for PostgreSQL
Collected Metadata
Data Process
A data process is a Matillion transformation.
  • Name
  • Source Description
  • Input: Input datasets
  • Output: Output datasets
  • Technical Data:
    • YAML job definition
    • Warehouse
    • Database
    • Schema
Unique Identifier Keys
A key is associated with each item of the catalog. When the object comes from an external system, the key is built and provided by the connector.
More information about unique identification keys in this documentation: Identification Keys.
Object
Identifier Key
Description
Data process
code/name
- code: Unique identifier of the connection noted in the configuration file
- name: job name
Last modified date: 11/28/2025