cancel
Showing results forย 
Search instead forย 
Did you mean:ย 
Data Engineering
Join discussions on data engineering best practices, architectures, and optimization strategies within the Databricks Community. Exchange insights and solutions with fellow data engineers.
cancel
Showing results forย 
Search instead forย 
Did you mean:ย 

pipeline config DAB

prakharsachan
New Contributor

I am deploying DLT pipeline in dev environment using DABs. source code is in a python script file. In the pipeline's yml file the configuration key is set to true(with all correct indentations), yet the pipeline isnt deploying in the continuous mode. Whats the reason?

1 ACCEPTED SOLUTION

Accepted Solutions

Hi @szymon_dybczak , just to clarify: I am already using continuous as a top-level property. However, I recently found a community post(replied by databricks employee) explaining that when a deployment occurs in development mode, the continuous setting is bypassed and the pipeline won't deploy in that modeโ€”even if the property is set to true. This setting only takes effect when deploying in production mode. I have also tested this fact.

View solution in original post

2 REPLIES 2

szymon_dybczak
Esteemed Contributor III

Hi @prakharsachan ,

Continuous must be set inside the pipeline resource definition, not under configuration.

The configuration block in a SDP (former DLT) pipeline definition is for Spark/pipeline settings (key-value string pairs passed to the runtime), not for pipeline deployment properties. So if you have something like:

szymon_dybczak_1-1776108303813.png

 

Databricks will just ignore it as an unrecognized Spark config. The fix is to promote continuous to a top-level property of the pipeline resource:

szymon_dybczak_0-1776108283652.png

 

 

 

 

Hi @szymon_dybczak , just to clarify: I am already using continuous as a top-level property. However, I recently found a community post(replied by databricks employee) explaining that when a deployment occurs in development mode, the continuous setting is bypassed and the pipeline won't deploy in that modeโ€”even if the property is set to true. This setting only takes effect when deploying in production mode. I have also tested this fact.