<?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 DLT with unity catalog and ML in Machine Learning</title>
    <link>https://community.databricks.com/t5/machine-learning/dlt-with-unity-catalog-and-ml/m-p/3880#M168</link>
    <description>&lt;P&gt;We are currently using DLT with unity catalog. DLT tables are created as materialized views in a schema inside a catalog. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When we try to access these materialized view using a ML runtime (ex. 13.0 ML) cluster, it says, that we must use Single User security mode. However, Single User security mode cannot access materialized views. It throws the error [MATERIALIZED_VIEW_OPRATION_NOT_ALLOWED.REQUIRES_SHARED_COMPUTE].&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is there any way to use DLT with unity catalog and ML all combined? We could create a notebook that copies the DLT materialized views into a Delta table but then there doesn't seem much of a point to using DLT.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Are we using DLT with Unity Catalog incorrectly? Should it only be used for bronze ingest/silver layer transformation and then we use Delta tables for gold layer tables?&lt;/P&gt;</description>
    <pubDate>Tue, 30 May 2023 13:50:15 GMT</pubDate>
    <dc:creator>oteng</dc:creator>
    <dc:date>2023-05-30T13:50:15Z</dc:date>
    <item>
      <title>DLT with unity catalog and ML</title>
      <link>https://community.databricks.com/t5/machine-learning/dlt-with-unity-catalog-and-ml/m-p/3880#M168</link>
      <description>&lt;P&gt;We are currently using DLT with unity catalog. DLT tables are created as materialized views in a schema inside a catalog. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When we try to access these materialized view using a ML runtime (ex. 13.0 ML) cluster, it says, that we must use Single User security mode. However, Single User security mode cannot access materialized views. It throws the error [MATERIALIZED_VIEW_OPRATION_NOT_ALLOWED.REQUIRES_SHARED_COMPUTE].&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is there any way to use DLT with unity catalog and ML all combined? We could create a notebook that copies the DLT materialized views into a Delta table but then there doesn't seem much of a point to using DLT.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Are we using DLT with Unity Catalog incorrectly? Should it only be used for bronze ingest/silver layer transformation and then we use Delta tables for gold layer tables?&lt;/P&gt;</description>
      <pubDate>Tue, 30 May 2023 13:50:15 GMT</pubDate>
      <guid>https://community.databricks.com/t5/machine-learning/dlt-with-unity-catalog-and-ml/m-p/3880#M168</guid>
      <dc:creator>oteng</dc:creator>
      <dc:date>2023-05-30T13:50:15Z</dc:date>
    </item>
    <item>
      <title>Re: DLT with unity catalog and ML</title>
      <link>https://community.databricks.com/t5/machine-learning/dlt-with-unity-catalog-and-ml/m-p/58991#M2937</link>
      <description>&lt;P&gt;I recently hit the same issue.&lt;BR /&gt;Seems like this is a limitation of DLT with Unity Catalog.&lt;BR /&gt;&lt;BR /&gt;Did you find a workaround&amp;nbsp;&lt;a href="https://community.databricks.com/t5/user/viewprofilepage/user-id/29629"&gt;@oteng&lt;/a&gt;? Otherwise I will try copying the materialized views to a table before doing the ML work.&lt;/P&gt;</description>
      <pubDate>Thu, 01 Feb 2024 15:54:18 GMT</pubDate>
      <guid>https://community.databricks.com/t5/machine-learning/dlt-with-unity-catalog-and-ml/m-p/58991#M2937</guid>
      <dc:creator>pg5</dc:creator>
      <dc:date>2024-02-01T15:54:18Z</dc:date>
    </item>
    <item>
      <title>Re: DLT with unity catalog and ML</title>
      <link>https://community.databricks.com/t5/machine-learning/dlt-with-unity-catalog-and-ml/m-p/59069#M2941</link>
      <description>&lt;P&gt;No workaround was found. We are just copying all the table to do the ML work. We haven't looked at this for a while though. So we are not aware of any new features.&lt;/P&gt;</description>
      <pubDate>Fri, 02 Feb 2024 15:45:29 GMT</pubDate>
      <guid>https://community.databricks.com/t5/machine-learning/dlt-with-unity-catalog-and-ml/m-p/59069#M2941</guid>
      <dc:creator>oteng</dc:creator>
      <dc:date>2024-02-02T15:45:29Z</dc:date>
    </item>
    <item>
      <title>Re: DLT with unity catalog and ML</title>
      <link>https://community.databricks.com/t5/machine-learning/dlt-with-unity-catalog-and-ml/m-p/59899#M2990</link>
      <description>&lt;P&gt;I managed to get some information from a friend at Databricks. Copying the tables in a separate workflow seems to be the best workaround for now.&lt;/P&gt;</description>
      <pubDate>Mon, 12 Feb 2024 08:20:11 GMT</pubDate>
      <guid>https://community.databricks.com/t5/machine-learning/dlt-with-unity-catalog-and-ml/m-p/59899#M2990</guid>
      <dc:creator>pg5</dc:creator>
      <dc:date>2024-02-12T08:20:11Z</dc:date>
    </item>
    <item>
      <title>Re: DLT with unity catalog and ML</title>
      <link>https://community.databricks.com/t5/machine-learning/dlt-with-unity-catalog-and-ml/m-p/71190#M3312</link>
      <description>&lt;P&gt;Is there any update on this? Basically you cannot access Materialized Views with ML Clsuters. To copy all tables for our Data Scientists seems like a really unnecessary step. Also they cannot profit from the advantage of the incremental table updates like others that can use shared cluster or SQL warehouses.&lt;/P&gt;</description>
      <pubDate>Fri, 31 May 2024 12:46:22 GMT</pubDate>
      <guid>https://community.databricks.com/t5/machine-learning/dlt-with-unity-catalog-and-ml/m-p/71190#M3312</guid>
      <dc:creator>MarkusFra</dc:creator>
      <dc:date>2024-05-31T12:46:22Z</dc:date>
    </item>
    <item>
      <title>Re: DLT with unity catalog and ML</title>
      <link>https://community.databricks.com/t5/machine-learning/dlt-with-unity-catalog-and-ml/m-p/71487#M3327</link>
      <description>&lt;P&gt;No updates as far as I am aware.&lt;BR /&gt;You could make the workflow copying the data smart though and try to only do incremental updates, seems like a lot of effort though.&lt;/P&gt;</description>
      <pubDate>Mon, 03 Jun 2024 14:22:17 GMT</pubDate>
      <guid>https://community.databricks.com/t5/machine-learning/dlt-with-unity-catalog-and-ml/m-p/71487#M3327</guid>
      <dc:creator>pg5</dc:creator>
      <dc:date>2024-06-03T14:22:17Z</dc:date>
    </item>
  </channel>
</rss>

