<?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: Why would I make a deep clone of a Delta table vs reading the table and writing a copy to a new location? in Data Engineering</title>
    <link>https://community.databricks.com/t5/data-engineering/why-would-i-make-a-deep-clone-of-a-delta-table-vs-reading-the/m-p/19585#M13142</link>
    <description>&lt;P&gt;A deep clone is recommended way as it holds the history of the table. Also, the DEEP clone is faster than the read-write approach. &lt;/P&gt;</description>
    <pubDate>Fri, 25 Jun 2021 21:29:24 GMT</pubDate>
    <dc:creator>brickster_2018</dc:creator>
    <dc:date>2021-06-25T21:29:24Z</dc:date>
    <item>
      <title>Why would I make a deep clone of a Delta table vs reading the table and writing a copy to a new location?</title>
      <link>https://community.databricks.com/t5/data-engineering/why-would-i-make-a-deep-clone-of-a-delta-table-vs-reading-the/m-p/19584#M13141</link>
      <description>&lt;P&gt;It seems like with both techniques I would end up with a copy of my table. Trying to understand when I should be using a deep clone.&lt;/P&gt;</description>
      <pubDate>Fri, 25 Jun 2021 16:11:58 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/why-would-i-make-a-deep-clone-of-a-delta-table-vs-reading-the/m-p/19584#M13141</guid>
      <dc:creator>User16826992666</dc:creator>
      <dc:date>2021-06-25T16:11:58Z</dc:date>
    </item>
    <item>
      <title>Re: Why would I make a deep clone of a Delta table vs reading the table and writing a copy to a new location?</title>
      <link>https://community.databricks.com/t5/data-engineering/why-would-i-make-a-deep-clone-of-a-delta-table-vs-reading-the/m-p/19585#M13142</link>
      <description>&lt;P&gt;A deep clone is recommended way as it holds the history of the table. Also, the DEEP clone is faster than the read-write approach. &lt;/P&gt;</description>
      <pubDate>Fri, 25 Jun 2021 21:29:24 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/why-would-i-make-a-deep-clone-of-a-delta-table-vs-reading-the/m-p/19585#M13142</guid>
      <dc:creator>brickster_2018</dc:creator>
      <dc:date>2021-06-25T21:29:24Z</dc:date>
    </item>
  </channel>
</rss>

