<?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: Is it required to run Lakeflow Connect on Serverless? in Data Engineering</title>
    <link>https://community.databricks.com/t5/data-engineering/is-it-required-to-run-lakeflow-connect-on-serverless/m-p/152511#M53837</link>
    <description>&lt;P&gt;Yes — Lakeflow Connect ingestion pipelines always run on Serverless compute.&amp;nbsp;&lt;/P&gt;&lt;DIV&gt;Databricks overrides your compute config and switches back to serverless,&lt;BR /&gt;because the ingestion connector &lt;EM&gt;requires&lt;/EM&gt; it.&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="saurabh18cs_0-1774868648207.png" style="width: 400px;"&gt;&lt;img src="https://community.databricks.com/t5/image/serverpage/image-id/25459i463D1CB53DBA394D/image-size/medium?v=v2&amp;amp;px=400" role="button" title="saurabh18cs_0-1774868648207.png" alt="saurabh18cs_0-1774868648207.png" /&gt;&lt;/span&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;&lt;DIV class=""&gt;&amp;nbsp;&lt;/DIV&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;/DIV&gt;</description>
    <pubDate>Mon, 30 Mar 2026 11:04:14 GMT</pubDate>
    <dc:creator>saurabh18cs</dc:creator>
    <dc:date>2026-03-30T11:04:14Z</dc:date>
    <item>
      <title>Is it required to run Lakeflow Connect on Serverless?</title>
      <link>https://community.databricks.com/t5/data-engineering/is-it-required-to-run-lakeflow-connect-on-serverless/m-p/152489#M53832</link>
      <description>&lt;P&gt;As the subject states, my question is:&lt;/P&gt;&lt;P&gt;Is it required to run the Ingestion Pipeline in Lakeflow Connect on Serverless compute? Cause I try to define my own cluster in the DAB, but it raises an error:&lt;/P&gt;&lt;P&gt;&lt;EM&gt;`Error: cannot create pipeline: You cannot provide cluster settings when using serverless compute.`&amp;nbsp;&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;Even though my serverless flag is set to false.&lt;/P&gt;</description>
      <pubDate>Mon, 30 Mar 2026 09:15:09 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/is-it-required-to-run-lakeflow-connect-on-serverless/m-p/152489#M53832</guid>
      <dc:creator>yit337</dc:creator>
      <dc:date>2026-03-30T09:15:09Z</dc:date>
    </item>
    <item>
      <title>Re: Is it required to run Lakeflow Connect on Serverless?</title>
      <link>https://community.databricks.com/t5/data-engineering/is-it-required-to-run-lakeflow-connect-on-serverless/m-p/152509#M53836</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.databricks.com/t5/user/viewprofilepage/user-id/210475"&gt;@yit337&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;For Lakeflow Connect managed ingestion pipelines, the behaviour you’re seeing is expected. As soon as you use ingestion_definition in your pipeline (i.e., a managed ingestion pipeline), Databricks forces that pipeline to run on serverless compute.&amp;nbsp;Serverless pipelines do not allow a clusters block. If you include cluster settings, you get the error you are seeing.&lt;/P&gt;
&lt;P&gt;You can refer to this documentation &lt;A href="https://docs.databricks.com/aws/en/ingestion/lakeflow-connect" target="_blank"&gt;page.&lt;/A&gt;&lt;/P&gt;
&lt;DIV id="tinyMceEditor_1448b808b66251Ashwin_DSA_0" class="mceNonEditable lia-copypaste-placeholder"&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-center" image-alt="lakeflowserverless.png" style="width: 999px;"&gt;&lt;img src="https://community.databricks.com/t5/image/serverpage/image-id/25458i7FDA842F491F46B7/image-size/large?v=v2&amp;amp;px=999" role="button" title="lakeflowserverless.png" alt="lakeflowserverless.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;FONT size="2" color="#FF6600"&gt;&lt;STRONG&gt;&lt;I&gt;If this answer resolves your question, could you mark it as “Accept as Solution”? That helps other users quickly find the correct fix.&lt;/I&gt;&lt;/STRONG&gt;&lt;/FONT&gt;&lt;I&gt;&lt;/I&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 30 Mar 2026 10:59:22 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/is-it-required-to-run-lakeflow-connect-on-serverless/m-p/152509#M53836</guid>
      <dc:creator>Ashwin_DSA</dc:creator>
      <dc:date>2026-03-30T10:59:22Z</dc:date>
    </item>
    <item>
      <title>Re: Is it required to run Lakeflow Connect on Serverless?</title>
      <link>https://community.databricks.com/t5/data-engineering/is-it-required-to-run-lakeflow-connect-on-serverless/m-p/152511#M53837</link>
      <description>&lt;P&gt;Yes — Lakeflow Connect ingestion pipelines always run on Serverless compute.&amp;nbsp;&lt;/P&gt;&lt;DIV&gt;Databricks overrides your compute config and switches back to serverless,&lt;BR /&gt;because the ingestion connector &lt;EM&gt;requires&lt;/EM&gt; it.&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="saurabh18cs_0-1774868648207.png" style="width: 400px;"&gt;&lt;img src="https://community.databricks.com/t5/image/serverpage/image-id/25459i463D1CB53DBA394D/image-size/medium?v=v2&amp;amp;px=400" role="button" title="saurabh18cs_0-1774868648207.png" alt="saurabh18cs_0-1774868648207.png" /&gt;&lt;/span&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;&lt;DIV class=""&gt;&amp;nbsp;&lt;/DIV&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;/DIV&gt;</description>
      <pubDate>Mon, 30 Mar 2026 11:04:14 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/is-it-required-to-run-lakeflow-connect-on-serverless/m-p/152511#M53837</guid>
      <dc:creator>saurabh18cs</dc:creator>
      <dc:date>2026-03-30T11:04:14Z</dc:date>
    </item>
  </channel>
</rss>

