Skip to main content
GCS Datalake

GCS Datalake

PROD
Feature List
✓ Metadata
✓ Data Profiler
✓ Data Quality
✓ Sample Data
✓ Auto-Classification
✕ Query Usage
✕ Lineage
✕ Column-level Lineage
✕ Owners
✕ dbt
✕ Tags
✕ Stored Procedures
In this section, we provide guides and references to use the GCS Datalake connector. Configure and schedule GCS Datalake metadata and profiler workflows from the OpenMetadata UI:

​
Requirements

Note: GCS Datalake connector supports extracting metadata from file types JSON, CSV, TSV & Parquet.

​
Python Requirements

We have support for Python versions 3.9-3.11
If running OpenMetadata version greater than 0.13, you will need to install the Datalake ingestion for GCS

​
GCS installation

pip3 install "openmetadata-ingestion[datalake-gcp]"

​
If version <0.13

You will be installing the requirements for GCS 
pip3 install "openmetadata-ingestion[datalake]"

​
Metadata Ingestion

All connectors are defined as JSON Schemas. Here you can find the structure to create a connection to Datalake. 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.

​
1. Define the YAML Config

​
2. Run with the CLI

First, we will need to save the YAML file. Afterward, and with all requirements installed, we can run: 
metadata ingest -c <path-to-yaml>
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.

​
dbt Integration

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