Adding a Google Dataplex (V2) Connection¶

Prerequisites¶

• A user with sufficient permissions is required to establish a connection with Dataplex.

• Zeenea traffic flows towards the data source must be open.

Supported Versions¶

The Dataplex connector was developed and tested with the web version of the product.

Installing the Plugin¶

You can download the Google plugin from Zeenea Connector Downloads.

For more information about how to install a plugin, see Installing and Configuring Connectors as a Plugin.

Declaring the Connection¶

Connectors are created and configured through a dedicated configuration file located in the /connections folder of the relevant scanner.

For more information about managing connections, see Managing Connections.

To establish a connection with a Dataplex instance, fill in the following parameters in the dedicated configuration file:

Universal Filters¶

Use the universal filter language to filter and root items based on the following criteria:

Example:

filters = [
  {
    id="accept_zeenea_dataset"
    action = ACCEPT
    rules {
      dataset = "ZEENEA*"
    }
  },
  {
    id = "default_reject"
    action = REJECT
  }
]

For more information about universal filters, see Universal Filters.

User Permissions¶

In order to collect metadata, the running user's permissions must allow them to access and read databases that need cataloging.

The user must have the following authorizations:

• dataplex.entryGroups.list
• dataplex.entryGroups.get
• dataplex.entries.list
• dataplex.entries.get

Data Extraction¶

To extract information, the connector runs the following request on the Google Dataplex API:

• projects.locations.entryGroups.list
• projects.locations.entryGroups.get
• projects.locations.entries.list
• projects.locations.entries.get

Collected Metadata¶

Inventory¶

Will collect the list of objects accessible by the user.

Dataset¶

A dataset is a Google Dataplex object.

• Name
• Source Description

• Technical Data:

  • Project Id
  • Location Id
  • Entry Id
  • Created At
  • Updated At
  • Type

Field¶

Dataset field.

• Name
• Source Description
• Type
• Can be null: Depending on the field settings.
• Multivalued: Not supported. Default value false.
• Primary Key: Depending on the "Primary Key" field attribute.

• Technical Data:

  • Technical Name
  • Native type

Unique Identifier Keys¶

Each object in the catalog is associated with a unique identifier key. When the object is imported from an external system, the key is generated and provided by the connector.

For more information about identifier keys, see Identification Keys.