v0.12.0 (2026-06-05)
What’s new
Added
- Spark Declarative Pipeline Orchestrator
PipelineNode.sources- a named dict of data sources replacing the singlesourcefield. All existingsource:YAML is automatically migrated tosources: {df: ...}.null_equals_nulloption forcdc_merge_options[#586]
Updated
- All laktory-injected Spark conf / pipeline configuration keys now use
laktory.namespace prefix (laktory.executor,laktory.requirements,laktory.config_filepath,laktory.pipeline_name) PipelineNode.execute()now reads allsourcesentries before invoking the transformer. Upstream nodes referenced via{nodes.X}SQL placeholders are pre-loaded here rather than insideDataFrameExprDtypeclass now supportstime_unitandtime_zoneproperties.- Databricks Terraform provider updated to 1.117.0
Fixed
- Table creation when cdc_merge_options with SCD_TYPE 2 is used
TableDataSinksupports "ORC" and "AVRO" formats
Breaking changes
- Renamed Databricks Pipelines orchestrator to Lakehouse Declarative Pipeline
- Refactored Lakehouse Declarative Pipeline script to use latest API (
apply_changes->create_auto_cdc_flow) - CLI
--dbks-job/--dbks-pipelineflags replaced by--databricks-job/--databricks-pipeline PipelineNode.sourcefield removed - usePipelineNode.sources(dict) instead. YAML usingsource:is automatically migrated; Python code accessing.sourcedirectly must be updated.- Renamed data sink
databricks_quality_monitortodatabricks_data_profiling_config - Removed pipeline
databricks_quality_monitors_enabledflag (now auto-detected) - Pipeline Lakeflow Job orchestrator data profiling configuration task is no longer active by default. Needs to set
data_profiling_config_tasktoTrue QualityMonitorresource renamed toDataQualityMonitorto be aligned with Databricks latest naming convention- Lakeflow Job data profiling task key renamed from
post-executetodata-profiling-configs
Full Changelog