<?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: Photon plan invariant violated Error in Data Engineering</title>
    <link>https://community.databricks.com/t5/data-engineering/photon-plan-invariant-violated-error/m-p/63249#M32200</link>
    <description>&lt;P&gt;Thank you&amp;nbsp;&lt;a href="https://community.databricks.com/t5/user/viewprofilepage/user-id/9"&gt;@Retired_mod&lt;/a&gt;! It looks like the issue was with a recent release on the databricks end, I'd raised a support ticket just to be sure, the difference also died down when we set these two up, at the cluster level.&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;spark.conf.set("spark.sql.adaptive.enabled", "true") &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;spark.conf.set("spark.sql.optimizer.excludedRules", "")&lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Mon, 11 Mar 2024 14:57:22 GMT</pubDate>
    <dc:creator>Vishwanath_Rao</dc:creator>
    <dc:date>2024-03-11T14:57:22Z</dc:date>
    <item>
      <title>Photon plan invariant violated Error</title>
      <link>https://community.databricks.com/t5/data-engineering/photon-plan-invariant-violated-error/m-p/62749#M32060</link>
      <description>&lt;P&gt;We've run into a niche error where we get the below message only on our non prod environment, with the same data, with the same code as our prod environment.&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;org.apache.spark.sql.execution.adaptive.InvalidAQEPlanException: Photon plan invariant violated: Broadcast joins have incompatible build plans regardingPhotonized vs. not-Photonized: ArrayBuffer(BroadcastHashJoin [COLUMN1#1372320], [COLUMN2#1422501], LeftOuter, BuildRight, false&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;Unsure as to what might be the issue, I've checked the spark logs, and it gives nothing on it as well, there doesn't seem to be any docs on these either. Any help is appreciated.&lt;/P&gt;</description>
      <pubDate>Wed, 06 Mar 2024 13:39:01 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/photon-plan-invariant-violated-error/m-p/62749#M32060</guid>
      <dc:creator>Vishwanath_Rao</dc:creator>
      <dc:date>2024-03-06T13:39:01Z</dc:date>
    </item>
    <item>
      <title>Re: Photon plan invariant violated Error</title>
      <link>https://community.databricks.com/t5/data-engineering/photon-plan-invariant-violated-error/m-p/63249#M32200</link>
      <description>&lt;P&gt;Thank you&amp;nbsp;&lt;a href="https://community.databricks.com/t5/user/viewprofilepage/user-id/9"&gt;@Retired_mod&lt;/a&gt;! It looks like the issue was with a recent release on the databricks end, I'd raised a support ticket just to be sure, the difference also died down when we set these two up, at the cluster level.&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;spark.conf.set("spark.sql.adaptive.enabled", "true") &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;spark.conf.set("spark.sql.optimizer.excludedRules", "")&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2024 14:57:22 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/photon-plan-invariant-violated-error/m-p/63249#M32200</guid>
      <dc:creator>Vishwanath_Rao</dc:creator>
      <dc:date>2024-03-11T14:57:22Z</dc:date>
    </item>
    <item>
      <title>Re: Photon plan invariant violated Error</title>
      <link>https://community.databricks.com/t5/data-engineering/photon-plan-invariant-violated-error/m-p/98055#M39593</link>
      <description>&lt;P&gt;Hey, did you raise a ticket and get a resolution to this?&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 07 Nov 2024 10:02:07 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/photon-plan-invariant-violated-error/m-p/98055#M39593</guid>
      <dc:creator>JAC2703</dc:creator>
      <dc:date>2024-11-07T10:02:07Z</dc:date>
    </item>
  </channel>
</rss>

