<?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 Unable to load historical data via DLT workflow in Data Engineering</title>
    <link>https://community.databricks.com/t5/data-engineering/unable-to-load-historical-data-via-dlt-workflow/m-p/44508#M27668</link>
    <description>&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;I'm trying to load historical data with the DLT workflow and facing a Out of Memory or Executor heartbeat lost error. The historical data loads fine with normal processing, but fails within DLT workflow. Tried repartitioning and scaling cluster, but no success.&lt;/P&gt;</description>
    <pubDate>Tue, 12 Sep 2023 19:47:29 GMT</pubDate>
    <dc:creator>Rpabs</dc:creator>
    <dc:date>2023-09-12T19:47:29Z</dc:date>
    <item>
      <title>Unable to load historical data via DLT workflow</title>
      <link>https://community.databricks.com/t5/data-engineering/unable-to-load-historical-data-via-dlt-workflow/m-p/44508#M27668</link>
      <description>&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;I'm trying to load historical data with the DLT workflow and facing a Out of Memory or Executor heartbeat lost error. The historical data loads fine with normal processing, but fails within DLT workflow. Tried repartitioning and scaling cluster, but no success.&lt;/P&gt;</description>
      <pubDate>Tue, 12 Sep 2023 19:47:29 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/unable-to-load-historical-data-via-dlt-workflow/m-p/44508#M27668</guid>
      <dc:creator>Rpabs</dc:creator>
      <dc:date>2023-09-12T19:47:29Z</dc:date>
    </item>
  </channel>
</rss>

