<?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 Delta live table segregation in Data Engineering</title>
    <link>https://community.databricks.com/t5/data-engineering/delta-live-table-segregation/m-p/72242#M34525</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp; &amp;nbsp;I've recently been prototyping on Databricks, I was hoping to develop using DLT pipelines in medallion architecture but with isolation of bronze/silver &amp;amp; gold layers in different catalogs in UC for security purposes.&lt;/P&gt;&lt;P&gt;At the moment is there a limitation whereby you are only able to use one DLT pipeline with a one to one relationship with a schema i.e all my tables will have to reside in the one schema?&lt;/P&gt;&lt;P&gt;Am I missing something obvious or is this the case? Any advice appreciated&lt;/P&gt;</description>
    <pubDate>Mon, 10 Jun 2024 15:01:58 GMT</pubDate>
    <dc:creator>Frustrated_DE</dc:creator>
    <dc:date>2024-06-10T15:01:58Z</dc:date>
    <item>
      <title>Delta live table segregation</title>
      <link>https://community.databricks.com/t5/data-engineering/delta-live-table-segregation/m-p/72242#M34525</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp; &amp;nbsp;I've recently been prototyping on Databricks, I was hoping to develop using DLT pipelines in medallion architecture but with isolation of bronze/silver &amp;amp; gold layers in different catalogs in UC for security purposes.&lt;/P&gt;&lt;P&gt;At the moment is there a limitation whereby you are only able to use one DLT pipeline with a one to one relationship with a schema i.e all my tables will have to reside in the one schema?&lt;/P&gt;&lt;P&gt;Am I missing something obvious or is this the case? Any advice appreciated&lt;/P&gt;</description>
      <pubDate>Mon, 10 Jun 2024 15:01:58 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/delta-live-table-segregation/m-p/72242#M34525</guid>
      <dc:creator>Frustrated_DE</dc:creator>
      <dc:date>2024-06-10T15:01:58Z</dc:date>
    </item>
    <item>
      <title>Re: Delta live table segregation</title>
      <link>https://community.databricks.com/t5/data-engineering/delta-live-table-segregation/m-p/72258#M34532</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.databricks.com/t5/user/viewprofilepage/user-id/99096"&gt;@Frustrated_DE&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;&lt;P&gt;This seems to be a long-requested feature based on this previous post:&amp;nbsp;&lt;A href="https://community.databricks.com/t5/data-engineering/dlt-pipeline/m-p/45742#M27975" target="_blank"&gt;Solved: Re: DLT pipeline - Databricks Community - 45740&lt;/A&gt;&lt;BR /&gt;An alternative solution maybe to delegate permissions on the table level for this pipeline specifically. Mirror the permissions given for each catalog onto each table instead.&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 10 Jun 2024 18:42:24 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/delta-live-table-segregation/m-p/72258#M34532</guid>
      <dc:creator>tyler-xorbix</dc:creator>
      <dc:date>2024-06-10T18:42:24Z</dc:date>
    </item>
  </channel>
</rss>

