<?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 Serverless Compute no support for Caching data frames in Data Engineering</title>
    <link>https://community.databricks.com/t5/data-engineering/serverless-compute-no-support-for-caching-data-frames/m-p/92323#M38403</link>
    <description>&lt;P&gt;Can anyone please tell me why df.cache() and df.persist() are not supported in Serevrless compute?&lt;/P&gt;&lt;P&gt;Many Thanks&lt;/P&gt;</description>
    <pubDate>Mon, 30 Sep 2024 15:05:28 GMT</pubDate>
    <dc:creator>Dave1967</dc:creator>
    <dc:date>2024-09-30T15:05:28Z</dc:date>
    <item>
      <title>Serverless Compute no support for Caching data frames</title>
      <link>https://community.databricks.com/t5/data-engineering/serverless-compute-no-support-for-caching-data-frames/m-p/92323#M38403</link>
      <description>&lt;P&gt;Can anyone please tell me why df.cache() and df.persist() are not supported in Serevrless compute?&lt;/P&gt;&lt;P&gt;Many Thanks&lt;/P&gt;</description>
      <pubDate>Mon, 30 Sep 2024 15:05:28 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/serverless-compute-no-support-for-caching-data-frames/m-p/92323#M38403</guid>
      <dc:creator>Dave1967</dc:creator>
      <dc:date>2024-09-30T15:05:28Z</dc:date>
    </item>
    <item>
      <title>Re: Serverless Compute no support for Caching data frames</title>
      <link>https://community.databricks.com/t5/data-engineering/serverless-compute-no-support-for-caching-data-frames/m-p/92330#M38406</link>
      <description>&lt;P&gt;Global caching functionality (and other global states used on classic clusters) is conceptually hard to represent on serverless computing.&lt;/P&gt;
&lt;P&gt;Serverless spark cluster optimizes the cache than the user.&lt;/P&gt;</description>
      <pubDate>Mon, 30 Sep 2024 15:32:02 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/serverless-compute-no-support-for-caching-data-frames/m-p/92330#M38406</guid>
      <dc:creator>gchandra</dc:creator>
      <dc:date>2024-09-30T15:32:02Z</dc:date>
    </item>
    <item>
      <title>Re: Serverless Compute no support for Caching data frames</title>
      <link>https://community.databricks.com/t5/data-engineering/serverless-compute-no-support-for-caching-data-frames/m-p/92338#M38411</link>
      <description>&lt;P&gt;Many Thanks&lt;/P&gt;</description>
      <pubDate>Mon, 30 Sep 2024 15:59:21 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/serverless-compute-no-support-for-caching-data-frames/m-p/92338#M38411</guid>
      <dc:creator>Dave1967</dc:creator>
      <dc:date>2024-09-30T15:59:21Z</dc:date>
    </item>
    <item>
      <title>Re: Serverless Compute no support for Caching data frames</title>
      <link>https://community.databricks.com/t5/data-engineering/serverless-compute-no-support-for-caching-data-frames/m-p/111414#M43888</link>
      <description>&lt;P&gt;What I do wish was possible was for serverless to warn that caching is not supported, but not error on a call. It makes switching between compute (serverless &amp;amp; all purpose) brittle and prevents code from easily being interoperable, no matter the compute type, which is significant friction against adopting serverless completely. Even having a parameter (i.e. .cache(try=True) ), would be nice to support this kind of workflow more elegantly.&lt;/P&gt;</description>
      <pubDate>Thu, 27 Feb 2025 21:49:21 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/serverless-compute-no-support-for-caching-data-frames/m-p/111414#M43888</guid>
      <dc:creator>kunalmishra9</dc:creator>
      <dc:date>2025-02-27T21:49:21Z</dc:date>
    </item>
    <item>
      <title>Re: Serverless Compute no support for Caching data frames</title>
      <link>https://community.databricks.com/t5/data-engineering/serverless-compute-no-support-for-caching-data-frames/m-p/119052#M45779</link>
      <description>&lt;P&gt;Hi. I'm not fully convinced that Serverless can optimize Spark cache better than the user, since I still see query plans with recomputed operations. What is the recommended best practice to avoid recomputation in a Serverless environment? Write out intermediate dataframes?&lt;/P&gt;</description>
      <pubDate>Tue, 13 May 2025 12:50:44 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/serverless-compute-no-support-for-caching-data-frames/m-p/119052#M45779</guid>
      <dc:creator>mrroger</dc:creator>
      <dc:date>2025-05-13T12:50:44Z</dc:date>
    </item>
  </channel>
</rss>

