<?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: DLT Pipeline issue in Data Engineering</title>
    <link>https://community.databricks.com/t5/data-engineering/dlt-pipeline-issue/m-p/143308#M52143</link>
    <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://community.databricks.com/t5/user/viewprofilepage/user-id/204040"&gt;@manjeetgahlawat&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;
&lt;P&gt;NoSuchElementException: key not found: test_bronze_dlt occurs when the table/view in the pipeline references a LIVE dataset named test_bronze_dlt, but DLT cannot find a dataset with that exact name in the pipeline graph. (So it never even gets to “reading files from the landing volume”.)&lt;/P&gt;
&lt;P&gt;You might have defined it as a qualified name like bronze.test_bronze_dlt (or catalog.bronze.test_bronze_dlt) but downstream code uses dlt.read_stream("test_bronze_dlt") or FROM LIVE.test_bronze_dlt.&lt;/P&gt;
&lt;P&gt;If you could provide&amp;nbsp; (a) the snippet that defines &lt;STRONG&gt;test_bronze_dlt&lt;/STRONG&gt; and (b) the first downstream table that reads it we can identify the cause . This is ideally a table definition issue.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 08 Jan 2026 09:05:41 GMT</pubDate>
    <dc:creator>K_Anudeep</dc:creator>
    <dc:date>2026-01-08T09:05:41Z</dc:date>
    <item>
      <title>DLT Pipeline issue</title>
      <link>https://community.databricks.com/t5/data-engineering/dlt-pipeline-issue/m-p/143287#M52139</link>
      <description>&lt;DIV class=""&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV&gt;&lt;SPAN class=""&gt;Hello Everyone,&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN class=""&gt;I have setup a DLT pipeline and while running it first time, I am getting the below issue:&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;SPAN class=""&gt;key not found: test_bronze_dlt&lt;/SPAN&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;SPAN class=""&gt;NoSuchElementException&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN class=""&gt;key not found: &lt;SPAN class=""&gt;test_bronze_dlt&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN class=""&gt;&lt;SPAN class=""&gt;test_bronze_dlt - this my DLT table name that is expected to be created in a bronze schema.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN class=""&gt;&lt;SPAN class=""&gt;I have verified that volume path exists in landing layer. DLT pipeline is able to create schema, but no progress after that.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN class=""&gt;&lt;SPAN class=""&gt;There is no other details except this message in the logs.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;</description>
      <pubDate>Thu, 08 Jan 2026 06:21:46 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/dlt-pipeline-issue/m-p/143287#M52139</guid>
      <dc:creator>manjeetgahlawat</dc:creator>
      <dc:date>2026-01-08T06:21:46Z</dc:date>
    </item>
    <item>
      <title>Re: DLT Pipeline issue</title>
      <link>https://community.databricks.com/t5/data-engineering/dlt-pipeline-issue/m-p/143308#M52143</link>
      <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://community.databricks.com/t5/user/viewprofilepage/user-id/204040"&gt;@manjeetgahlawat&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;
&lt;P&gt;NoSuchElementException: key not found: test_bronze_dlt occurs when the table/view in the pipeline references a LIVE dataset named test_bronze_dlt, but DLT cannot find a dataset with that exact name in the pipeline graph. (So it never even gets to “reading files from the landing volume”.)&lt;/P&gt;
&lt;P&gt;You might have defined it as a qualified name like bronze.test_bronze_dlt (or catalog.bronze.test_bronze_dlt) but downstream code uses dlt.read_stream("test_bronze_dlt") or FROM LIVE.test_bronze_dlt.&lt;/P&gt;
&lt;P&gt;If you could provide&amp;nbsp; (a) the snippet that defines &lt;STRONG&gt;test_bronze_dlt&lt;/STRONG&gt; and (b) the first downstream table that reads it we can identify the cause . This is ideally a table definition issue.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 08 Jan 2026 09:05:41 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/dlt-pipeline-issue/m-p/143308#M52143</guid>
      <dc:creator>K_Anudeep</dc:creator>
      <dc:date>2026-01-08T09:05:41Z</dc:date>
    </item>
  </channel>
</rss>

