Hi @ashraf1395 Yes, your understanding is partially correct. Let me clarify:Only one pipeline can own and manage a target table, including operations like schema evolution, maintenance, and refreshes, etcWhen other pipelines are mentioned as "produci...
Hi @sakuraDev , this looks like a Soda syntax issue.
Try fixing the "fail" and "warn" fields in your Soda checks. For example, instead of writing:
- missing_count(site) = 0:
name: Ensure no null values
fail: 1
warn: 0
Use Soda's thres...
Hi @ashraf1395 ,
Unfortunately, it’s not possible to achieve this using append_flow or similar approaches across multiple pipelines. Delta Live Tables are designed so that each target table is managed and owned by a single pipeline. This means mainte...
Hi @Jorge3, where you able to get this issue resolved?
I believe your artifact build path points outside the synced directory structure, and after syncing ../libs, libs should be available within the bundle root, so the artifact path should be update...
Hi @Data_Engineer07 ,
Please reach out through https://www.databricks.com/company/contact regarding such requests. The corresponding team will guide on this request and let you know of its availability if there is.
