DLT release 2022.40
September 28 - October 5, 2022
These features and improvements were released with the 2022.40 release of DLT.
Databricks Runtime versions used by this release
Channel:
- CURRENT (default): Databricks Runtime 11.0.7
- PREVIEW: Databricks Runtime 11.0.7
New features and improvements in this release
- Using a cluster label other than
defaultormaintenancein your pipeline settings causes failures during pipeline creation or edit. For more information about cluster configuration for Lakeflow Declarative Pipelines, see Configure classic compute for Lakeflow Declarative Pipelines.
- You can now open or run pipelines directly from your Lakeflow Declarative Pipelines notebooks. See Develop and debug ETL pipelines with a notebook in Lakeflow Declarative Pipelines.
- This release includes a breaking change in the pipeline settings data structure returned by DLT API requests. This change returns the
editionfield as an upper case value. Previously, this value was returned as mixed case. You must update your clients that read theeditionvalue in API responses to ensure the correct processing of the return value. However, theeditionvalue in API requests is case insensitive; your clients that submit requests including this field do not require updating.
Bug Fixes in this release
- This release fixes a bug that causes the DLT UI to show a pipeline in a
RUNNINGstate even after update failure.
- This update fixes a bug in the APPLY_CHANGES interface when re-processing input data where the data contains duplicate
DELETEoperations with the same value in theSEQUENCEcolumn. This scenario results inNULLvalues in the target table and removal of theDeleteVersionvalue. This is equivalent to marking the record asNOT-DELETED. With this change, the duplicateDELETEoperations are handled idempotently and always mark the record asDELETED.
- This release fixes a bug causing rows to be hidden during SCD type 2 processing when a previous historical record is deleted containing the same columns as the next historical record.
- This update fixes a bug causing a view with an
expect_or_failexpectation to remain in theRUNNINGstate even if the expectation fails. With this fix, the pipeline fails and transitions to theFAILEDstate.