<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Delta Live Table run outside out pipeline in Data Engineering</title>
    <link>https://community.databricks.com/t5/data-engineering/delta-live-table-run-outside-out-pipeline/m-p/82119#M36526</link>
    <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.databricks.com/t5/user/viewprofilepage/user-id/114079"&gt;@ruoyuqian&lt;/a&gt; Delta Live Tables (DLT) have specific execution contexts and dependencies that are managed within their pipeline environment. This is why the code runs successfully only when executed within the pipeline, as DLT creates its own job cluster tailored to its dependencies rather than relying on a dedicated cluster. If you're concerned about costs, I recommend reviewing Databricks' compute pricing and exploring optimization strategies to reduce expenses effectively&lt;/P&gt;</description>
    <pubDate>Wed, 07 Aug 2024 05:55:43 GMT</pubDate>
    <dc:creator>Rishabh-Pandey</dc:creator>
    <dc:date>2024-08-07T05:55:43Z</dc:date>
    <item>
      <title>Delta Live Table run outside out pipeline</title>
      <link>https://community.databricks.com/t5/data-engineering/delta-live-table-run-outside-out-pipeline/m-p/82115#M36524</link>
      <description>&lt;P&gt;I have created a notebook for my Delta Live Table pipeline and it runs without errors however if I run the notebook alone in my cluster it,&amp;nbsp; says not allowed and show this error.&amp;nbsp; Does it mean I can only run delta live table in the pipeline and cannot run locally on a cluster? because if I run it via DLT it will cost me extra money to do so.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;LI-CODE lang="python"&gt;import dlt
from pyspark.sql.functions import *
from pyspark.sql.functions import col, trim, split, concat, current_timestamp, row_number, expr, hash as pyspark_hash
from pyspark.sql.window import Window

The Delta Live Tables (DLT) module is not supported on this cluster. You should either create a new pipeline or use an existing pipeline to run DLT code.&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 07 Aug 2024 05:12:18 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/delta-live-table-run-outside-out-pipeline/m-p/82115#M36524</guid>
      <dc:creator>ruoyuqian</dc:creator>
      <dc:date>2024-08-07T05:12:18Z</dc:date>
    </item>
    <item>
      <title>Re: Delta Live Table run outside out pipeline</title>
      <link>https://community.databricks.com/t5/data-engineering/delta-live-table-run-outside-out-pipeline/m-p/82119#M36526</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.databricks.com/t5/user/viewprofilepage/user-id/114079"&gt;@ruoyuqian&lt;/a&gt; Delta Live Tables (DLT) have specific execution contexts and dependencies that are managed within their pipeline environment. This is why the code runs successfully only when executed within the pipeline, as DLT creates its own job cluster tailored to its dependencies rather than relying on a dedicated cluster. If you're concerned about costs, I recommend reviewing Databricks' compute pricing and exploring optimization strategies to reduce expenses effectively&lt;/P&gt;</description>
      <pubDate>Wed, 07 Aug 2024 05:55:43 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/delta-live-table-run-outside-out-pipeline/m-p/82119#M36526</guid>
      <dc:creator>Rishabh-Pandey</dc:creator>
      <dc:date>2024-08-07T05:55:43Z</dc:date>
    </item>
  </channel>
</rss>

