<?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 Optimistic Transactions Resolution and Exceptions in Data Engineering</title>
    <link>https://community.databricks.com/t5/data-engineering/delta-optimistic-transactions-resolution-and-exceptions/m-p/21008#M14249</link>
    <description>&lt;P&gt;While you can try-catch-retry , it would be expensive to retry as the underlying table snapshot would have changed. So the best approach is to &lt;A href="https://docs.databricks.com/delta/concurrency-control.html#avoid-conflicts-using-partitioning-and-disjoint-command-conditions" alt="https://docs.databricks.com/delta/concurrency-control.html#avoid-conflicts-using-partitioning-and-disjoint-command-conditions" target="_blank"&gt;avoid conflicts using partitioning and disjoint command conditions as much as possible.&lt;/A&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;</description>
    <pubDate>Thu, 24 Jun 2021 04:22:18 GMT</pubDate>
    <dc:creator>sajith_appukutt</dc:creator>
    <dc:date>2021-06-24T04:22:18Z</dc:date>
    <item>
      <title>Delta Optimistic Transactions Resolution and Exceptions</title>
      <link>https://community.databricks.com/t5/data-engineering/delta-optimistic-transactions-resolution-and-exceptions/m-p/21006#M14247</link>
      <description>&lt;P&gt;What is the best way to deal with concurrent exceptions in Delta when you have multiple writers on the same delta table ?  &lt;/P&gt;</description>
      <pubDate>Thu, 24 Jun 2021 01:55:35 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/delta-optimistic-transactions-resolution-and-exceptions/m-p/21006#M14247</guid>
      <dc:creator>User16783853501</dc:creator>
      <dc:date>2021-06-24T01:55:35Z</dc:date>
    </item>
    <item>
      <title>Re: Delta Optimistic Transactions Resolution and Exceptions</title>
      <link>https://community.databricks.com/t5/data-engineering/delta-optimistic-transactions-resolution-and-exceptions/m-p/21007#M14248</link>
      <description>&lt;P&gt;Delta operations that can result in a conflict with multiple writers can be found here - &lt;A href="https://docs.databricks.com/delta/concurrency-control.html#write-conflicts.In" target="test_blank"&gt;https://docs.databricks.com/delta/concurrency-control.html#write-conflicts.In&lt;/A&gt; all cases marked “can conflict”, whether the two operations will conflict depends on whether they operate on the same set of files. You can make the two sets of files disjoint by partitioning the table by the same columns as those used in the conditions of the operations&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;As a general rule the ideas would be the defined your predicates in such a way that concurrent writers operate on different partitions/files of a delta table to avoid concurrent write exceptions&lt;/P&gt;</description>
      <pubDate>Thu, 24 Jun 2021 03:08:17 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/delta-optimistic-transactions-resolution-and-exceptions/m-p/21007#M14248</guid>
      <dc:creator>aladda</dc:creator>
      <dc:date>2021-06-24T03:08:17Z</dc:date>
    </item>
    <item>
      <title>Re: Delta Optimistic Transactions Resolution and Exceptions</title>
      <link>https://community.databricks.com/t5/data-engineering/delta-optimistic-transactions-resolution-and-exceptions/m-p/21008#M14249</link>
      <description>&lt;P&gt;While you can try-catch-retry , it would be expensive to retry as the underlying table snapshot would have changed. So the best approach is to &lt;A href="https://docs.databricks.com/delta/concurrency-control.html#avoid-conflicts-using-partitioning-and-disjoint-command-conditions" alt="https://docs.databricks.com/delta/concurrency-control.html#avoid-conflicts-using-partitioning-and-disjoint-command-conditions" target="_blank"&gt;avoid conflicts using partitioning and disjoint command conditions as much as possible.&lt;/A&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 24 Jun 2021 04:22:18 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/delta-optimistic-transactions-resolution-and-exceptions/m-p/21008#M14249</guid>
      <dc:creator>sajith_appukutt</dc:creator>
      <dc:date>2021-06-24T04:22:18Z</dc:date>
    </item>
  </channel>
</rss>

