<?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: Failed to edit ingestion pipeline PostgreSQL slot name cannot be empty or null in Data Engineering</title>
    <link>https://community.databricks.com/t5/data-engineering/failed-to-edit-ingestion-pipeline-postgresql-slot-name-cannot-be/m-p/139581#M51237</link>
    <description>&lt;P&gt;After I posted this I noticed that the gateway compute for this pipeline was repeatedly failing and retrying. This was resolved by increasing our quota of "Standard FS Family" compute on Azure. And when that was resolved the above error also disappeared. So my bad for not checking the gateway first but just between you and me, should that have been the right error message?&lt;/P&gt;</description>
    <pubDate>Wed, 19 Nov 2025 00:01:13 GMT</pubDate>
    <dc:creator>dbernstein_tp</dc:creator>
    <dc:date>2025-11-19T00:01:13Z</dc:date>
    <item>
      <title>Failed to edit ingestion pipeline PostgreSQL slot name cannot be empty or null</title>
      <link>https://community.databricks.com/t5/data-engineering/failed-to-edit-ingestion-pipeline-postgresql-slot-name-cannot-be/m-p/139562#M51229</link>
      <description>&lt;P&gt;I'm trying to add tables to an existing SQL server CDC ingestion pipeline and today am getting this mysterious error message.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;DIV class=""&gt;Failed to edit ingestion pipeline&lt;/DIV&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV&gt;&lt;DIV&gt;PostgreSQL slot name cannot be empty or null&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;Have not encountered this before. Is this simply a bug in the latest rollout?&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;</description>
      <pubDate>Tue, 18 Nov 2025 18:45:17 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/failed-to-edit-ingestion-pipeline-postgresql-slot-name-cannot-be/m-p/139562#M51229</guid>
      <dc:creator>dbernstein_tp</dc:creator>
      <dc:date>2025-11-18T18:45:17Z</dc:date>
    </item>
    <item>
      <title>Re: Failed to edit ingestion pipeline PostgreSQL slot name cannot be empty or null</title>
      <link>https://community.databricks.com/t5/data-engineering/failed-to-edit-ingestion-pipeline-postgresql-slot-name-cannot-be/m-p/139581#M51237</link>
      <description>&lt;P&gt;After I posted this I noticed that the gateway compute for this pipeline was repeatedly failing and retrying. This was resolved by increasing our quota of "Standard FS Family" compute on Azure. And when that was resolved the above error also disappeared. So my bad for not checking the gateway first but just between you and me, should that have been the right error message?&lt;/P&gt;</description>
      <pubDate>Wed, 19 Nov 2025 00:01:13 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/failed-to-edit-ingestion-pipeline-postgresql-slot-name-cannot-be/m-p/139581#M51237</guid>
      <dc:creator>dbernstein_tp</dc:creator>
      <dc:date>2025-11-19T00:01:13Z</dc:date>
    </item>
  </channel>
</rss>

