Registry / data / dlt-meta

dlt-meta

JSON →
library0.0.10pypypiunverified

DLT-META is a metadata-driven framework for Databricks Lakeflow Declarative Pipelines, designed to automate the creation and management of bronze and silver data pipelines. It leverages metadata defined in JSON or YAML files to dynamically generate pipeline code, streamlining data engineering workflows. The library is currently at version 0.0.10 and has active, though irregular, release cycles with consistent updates.

pip install dlt-meta
INSTALL
IMPORT
SIG · DLT-META
D
dlt-meta
datapythonv0.0.10
Install
4.9s avg
Import
Disk
62MB
Pass rate
10/ 10
Env Coverage10 / 10
glibc
3.93.13
musl
3.93.13
Install & Compatibility
Where this runs
tested against v0.0.10 · pip install
no network on importno background threads
Install × environment matrix
Each cell = how many times install + import succeeded across repeated harness runs. Partial = flaky.
glibc = Debian/Ubuntu slim · musl = Alpine Linux
musl
py 3.103.915 runs
installs and imports cleanly · install 0.0s · import 0.000s · 57.5MB
glibc
py 3.103.915 runs
installs and imports cleanly · install 4.9s · import 0.000s · 59MB
62MB installed
● package 62MB
Code
Verified usage

Verified import paths — ran on the pinned version, not inferred.

DataflowPipeline
from dlt_meta.src import DataflowPipeline
from dlt_meta.src import DataflowPipeline

This quickstart demonstrates how to programmatically invoke the `dlt-meta` framework within a Databricks environment (typically a notebook or job). It assumes `dlt-meta` is installed and metadata has been onboarded. The `DataflowPipeline.invoke_dlt_pipeline` method orchestrates the creation and execution of DLT pipelines based on the provided layer and environment, reading from pre-configured metadata.

# This code typically runs within a Databricks Notebook or job after metadata onboarding. # Ensure 'dlt-meta' is installed via %pip install dlt-meta in the notebook or as a cluster library. import dlt from dlt_meta import DataflowPipeline import os # These parameters would typically be passed as job parameters in Databricks # For local testing, you might set environment variables or hardcode. layer = os.environ.get('DLT_META_LAYER', 'bronze').lower() # e.g., 'bronze' or 'silver' env = os.environ.get('DLT_META_ENV', 'dev').lower() # e.g., 'dev', 'qa', 'prod' # In a Databricks environment, 'spark' session is implicitly available. # For local testing outside Databricks, you would need to initialize a SparkSession. # Example placeholder for local SparkSession (not typically done in DLT-META's primary use-case): # from pyspark.sql import SparkSession # spark = SparkSession.builder.appName("dlt-meta-local").getOrCreate() try: print(f"Attempting to invoke DLT-META for layer: {layer} (env: {env}).") # The 'spark' object is expected to be the Databricks SparkSession DataflowPipeline.invoke_dlt_pipeline(spark=spark, layer=layer, env=env) print(f"DLT-META successfully invoked for layer: {layer} (env: {env}).") except ImportError: print("ERROR: Could not import DataflowPipeline from dlt_meta. Ensure the 'dlt-meta' library is installed and available.") raise except Exception as e: print(f"ERROR: An exception occurred during DLT-META pipeline invocation for layer '{layer}' in env '{env}': {e}") raise
Debug
Known issues
breakingThe DPM (Direct Publishing Mode) flag was removed in v0.0.10. Pipelines using DPM mode in v0.0.9 must be migrated to the default publishing mode before upgrading. This change is metadata-only but irreversible.
fix
Migrate existing pipelines from DPM mode to the default publishing mode as per Databricks' migration guide.
affects: >=0.0.10
breakingMulti-Level Namespace Changes in v0.0.10. Custom schema qualification in table names is no longer supported; tables must be created without database qualifiers.
fix
Remove database qualifiers from table names in your metadata (e.g., change `database.schema.table` to `schema.table` or `table`).
affects: >=0.0.10
breakingArgument changes for `invoke_dlt_pipeline` in v0.0.10. Method arguments now require `bronze_` or `silver_` prefixes to support `apply_changes_from_snapshot` in both layers.
fix
Update existing pipeline configurations to use the new layer-specific argument prefixes (e.g., `bronze_arg` or `silver_arg`).
affects: >=0.0.10
gotchaDLT-META is a Databricks Labs project and is provided for exploration only. Databricks does not formally support it or provide SLAs. Do not submit Databricks support tickets for issues; instead, file a GitHub issue.
fix
For issues, report them directly on the dlt-meta GitHub repository.
affects: All versions
gotchaMalformed JSON/YAML metadata can lead to job failures. The framework relies heavily on correct metadata structure and content.
fix
Validate onboarding JSON/YAML against a predefined schema before ingestion. Ensure all required fields are present and data types are correct.
affects: All versions
Upgrade
Version history
0.0.10latest on PyPI · released Sep 16, 2025
Audit
Dependencies
pythonrequiredRequired runtime environment.
databricks-clirequiredRequired for CLI interactions and deployment to Databricks workspace (v0.213 or later).
PyYAMLoptionalUsed for parsing YAML metadata files.
setuptoolsoptionalCore dependency for Python package management.
databricks-sdkoptionalUsed for interacting with Databricks APIs.
Agent activity
24 hits · last 30 days
node
22
OpenAI (training)
1
Resources