Run Redshift using the metadata CLI

FeatureStatus
StagePROD
Metadata
Query Usage
Data Profiler
Data Quality
Lineage
DBT
Supported Versions--
FeatureStatus
Lineage
Table-level
Column-level

In this section, we provide guides and references to use the Redshift connector.

Configure and schedule Redshift metadata and profiler workflows from the OpenMetadata UI:

OpenMetadata 0.12 or later

To deploy OpenMetadata, check the Deployment guides.

To run the Ingestion via the UI you'll need to use the OpenMetadata Ingestion Container, which comes shipped with custom Airflow plugins to handle the workflow deployment.

Redshift user must grant SELECT privilege on table SVV_TABLE_INFO to fetch the metadata of tables and views. For more information visit here.

To run the Redshift ingestion, you will need to install:

If you want to run the Usage Connector, you'll also need to install:

All connectors are defined as JSON Schemas. Here you can find the structure to create a connection to Redshift.

In order to create and run a Metadata Ingestion workflow, we will follow the steps to create a YAML configuration able to connect to the source, process the Entities if needed, and reach the OpenMetadata server.

The workflow is modeled around the following JSON Schema

Note: During the metadata ingestion for redshift, the tables in which the distribution style i.e DISTSTYLE is not AUTO will be marked as partitioned tables

This is a sample config for Redshift:

username: Specify the User to connect to Snoflake. It should have enough privileges to read all the metadata.

password: Password to connect to Redshift.

database: The database of the data source is an optional parameter, if you would like to restrict the metadata reading to a single database. If left blank, OpenMetadata ingestion attempts to scan all the databases.

hostPort: Host and port of the Redshift service.

ingestAllDatabases: Ingest data from all databases in Redshift. You can use databaseFilterPattern on top of this.

The sourceConfig is defined here:

markDeletedTables: To flag tables as soft-deleted if they are not present anymore in the source system.

includeTables: true or false, to ingest table data. Default is true.

includeViews: true or false, to ingest views definitions.

databaseFilterPattern, schemaFilterPattern, tableFilternPattern: Note that the filter supports regex as include or exclude. You can find examples here

To send the metadata to OpenMetadata, it needs to be specified as type: metadata-rest.

The main property here is the openMetadataServerConfig, where you can define the host and security provider of your OpenMetadata installation.

For a simple, local installation using our docker containers, this looks like:

Connection Options (Optional): Enter the details for any additional connection options that can be sent to Athena during the connection. These details must be added as Key-Value pairs.

Connection Arguments (Optional): Enter the details for any additional connection arguments such as security or protocol configs that can be sent to Athena during the connection. These details must be added as Key-Value pairs.

  • In case you are using Single-Sign-On (SSO) for authentication, add the authenticator details in the Connection Arguments as a Key-Value pair as follows: "authenticator" : "sso_login_url"
  • In case you authenticate with SSO using an external browser popup, then add the authenticator details in the Connection Arguments as a Key-Value pair as follows: "authenticator" : "externalbrowser"
filename.yaml

We support different security providers. You can find their definitions here.

  • JWT tokens will allow your clients to authenticate against the OpenMetadata server. To enable JWT Tokens, you will get more details here.
  • You can refer to the JWT Troubleshooting section link for any issues in your JWT configuration. If you need information on configuring the ingestion with other security providers in your bots, you can follow this doc link.

First, we will need to save the YAML file. Afterward, and with all requirements installed, we can run:

Note that from connector to connector, this recipe will always be the same. By updating the YAML configuration, you will be able to extract metadata from different sources.

The Query Usage workflow will be using the query-parser processor.

After running a Metadata Ingestion workflow, we can run Query Usage workflow. While the serviceName will be the same to that was used in Metadata Ingestion, so the ingestion bot can get the serviceConnection details from the server.

This is a sample config for Redshift Usage:

You can find all the definitions and types for the sourceConfig here.

queryLogDuration: Configuration to tune how far we want to look back in query logs to process usage data.

stageFileLocation: Temporary file name to store the query logs before processing. Absolute file path required.

resultLimit: Configuration to set the limit for query logs

queryLogFilePath: Configuration to set the file path for query logs

To specify where the staging files will be located.

Note that the location is a directory that will be cleaned at the end of the ingestion.

The main property here is the openMetadataServerConfig, where you can define the host and security provider of your OpenMetadata installation.

For a simple, local installation using our docker containers, this looks like:

filename.yaml

There is an extra requirement to run the Usage pipelines. You will need to install:

After saving the YAML config, we will run the command the same way we did for the metadata ingestion:

The Data Profiler workflow will be using the orm-profiler processor.

After running a Metadata Ingestion workflow, we can run Data Profiler workflow. While the serviceName will be the same to that was used in Metadata Ingestion, so the ingestion bot can get the serviceConnection details from the server.

This is a sample config for the profiler:

You can find all the definitions and types for the sourceConfig here.

generateSampleData: Option to turn on/off generating sample data.

profileSample: Percentage of data or no. of rows we want to execute the profiler and tests on.

threadCount: Number of threads to use during metric computations.

processPiiSensitive: Optional configuration to automatically tag columns that might contain sensitive information.

confidence: Set the Confidence value for which you want the column to be marked

timeoutSeconds: Profiler Timeout in Seconds

databaseFilterPattern: Regex to only fetch databases that matches the pattern.

schemaFilterPattern: Regex to only fetch tables or databases that matches the pattern.

tableFilterPattern: Regex to only fetch tables or databases that matches the pattern.

Choose the orm-profiler. Its config can also be updated to define tests from the YAML itself instead of the UI:

tableConfig: tableConfig allows you to set up some configuration at the table level.

To send the metadata to OpenMetadata, it needs to be specified as type: metadata-rest.

The main property here is the openMetadataServerConfig, where you can define the host and security provider of your OpenMetadata installation.

For a simple, local installation using our docker containers, this looks like:

filename.yaml
  • You can learn more about how to configure and run the Profiler Workflow to extract Profiler data and execute the Data Quality from here

Here, we follow a similar approach as with the metadata and usage pipelines, although we will use a different Workflow class:

The ProfilerWorkflow class that is being imported is a part of a metadata orm_profiler framework, which defines a process of extracting Profiler data.

Here we are also importing all the basic requirements to parse YAMLs, handle dates and build our DAG.

Default arguments for all tasks in the Airflow DAG.

  • Default arguments dictionary contains default arguments for tasks in the DAG, including the owner's name, email address, number of retries, retry delay, and execution timeout.
  • config: Specifies config for the profiler as we prepare above.
  • metadata_ingestion_workflow(): This code defines a function metadata_ingestion_workflow() that loads a YAML configuration, creates a ProfilerWorkflow object, executes the workflow, checks its status, prints the status to the console, and stops the workflow.
  • DAG: creates a DAG using the Airflow framework, and tune the DAG configurations to whatever fits with your requirements
  • For more Airflow DAGs creation details visit here.
filename.py

In order to integrate SSL in the Metadata Ingestion Config, the user will have to add the SSL config under connectionArguments which is placed in the source.

There are couple of types of SSL modes that Redshift supports which can be added to ConnectionArguments, they are as follows:

  • disable: SSL is disabled and the connection is not encrypted.

  • allow: SSL is used if the server requires it.

  • prefer: SSL is used if the server supports it. Amazon Redshift supports SSL, so SSL is used when you set sslmode to prefer.

  • require: SSL is required.

  • verify-ca: SSL must be used and the server certificate must be verified.

  • verify-full: SSL must be used. The server certificate must be verified and the server hostname must match the hostname attribute on the certificate.

For more information, you can visit Redshift SSL documentation

filename.yaml

You can learn more about how to ingest lineage here.

You can learn more about how to ingest dbt models' definitions and their lineage here.