<?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 LEGACY_SINGLE_USER_STANDARD no longer supported? in Data Engineering</title>
    <link>https://community.databricks.com/t5/data-engineering/is-legacy-single-user-standard-no-longer-supported/m-p/8048#M3776</link>
    <description>&lt;P&gt;...and it works again - no changes made by us&lt;/P&gt;</description>
    <pubDate>Wed, 24 May 2023 12:16:34 GMT</pubDate>
    <dc:creator>grazie</dc:creator>
    <dc:date>2023-05-24T12:16:34Z</dc:date>
    <item>
      <title>Is LEGACY_SINGLE_USER_STANDARD no longer supported?</title>
      <link>https://community.databricks.com/t5/data-engineering/is-legacy-single-user-standard-no-longer-supported/m-p/8044#M3772</link>
      <description>&lt;P&gt;Based on [an  answer in this community](https://community.databricks.com/s/question/0D58Y00009jfKM1SAM/error-no-metastore-assigned-for-the-current-workspace), we set "data security mode" to LEGACY_SINGLE_USER_STANDARD in a cluster policy which needed to access files through dbutil.fs in a workspace and that previously got the NO METASTORE error that the above answer resolved.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;However, now I was unable to create a cluster using this policy - could it be that LEGACY_SINGLE_USER_STANDARD is no longer supported? I looked in release notes, but couldn't find info about that there.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If so, what is the approach to solve the same issue now?&lt;/P&gt;</description>
      <pubDate>Thu, 09 Mar 2023 06:28:18 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/is-legacy-single-user-standard-no-longer-supported/m-p/8044#M3772</guid>
      <dc:creator>grazie</dc:creator>
      <dc:date>2023-03-09T06:28:18Z</dc:date>
    </item>
    <item>
      <title>Re: Is LEGACY_SINGLE_USER_STANDARD no longer supported?</title>
      <link>https://community.databricks.com/t5/data-engineering/is-legacy-single-user-standard-no-longer-supported/m-p/8045#M3773</link>
      <description>&lt;P&gt;@Geir Iversen​&amp;nbsp;Below cluster policy works for me. BTW access to the file system is allowed in single user mode in Unity Catalog. Did you try this access mode?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;"data_security_mode": {&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;"type": "allowlist",&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;"values": [&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;"SINGLE_USER",&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;"LEGACY_SINGLE_USER",&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;"LEGACY_SINGLE_USER_STANDARD"&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;],&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;"defaultValue": "SINGLE_USER",&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;"hidden": true&lt;/P&gt;&lt;P&gt;&amp;nbsp;},&lt;/P&gt;</description>
      <pubDate>Sat, 11 Mar 2023 14:52:05 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/is-legacy-single-user-standard-no-longer-supported/m-p/8045#M3773</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2023-03-11T14:52:05Z</dc:date>
    </item>
    <item>
      <title>Re: Is LEGACY_SINGLE_USER_STANDARD no longer supported?</title>
      <link>https://community.databricks.com/t5/data-engineering/is-legacy-single-user-standard-no-longer-supported/m-p/8046#M3774</link>
      <description>&lt;P&gt;changing to SINGLE_USER in the policy allowed us to create clusters, and they didn't have the "NO METASTORE issue". &lt;/P&gt;</description>
      <pubDate>Tue, 21 Mar 2023 11:03:46 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/is-legacy-single-user-standard-no-longer-supported/m-p/8046#M3774</guid>
      <dc:creator>grazie</dc:creator>
      <dc:date>2023-03-21T11:03:46Z</dc:date>
    </item>
    <item>
      <title>Re: Is LEGACY_SINGLE_USER_STANDARD no longer supported?</title>
      <link>https://community.databricks.com/t5/data-engineering/is-legacy-single-user-standard-no-longer-supported/m-p/8047#M3775</link>
      <description>&lt;P&gt;Now we do have this issue again, starting today. With the SINGLE_USER access mode&lt;/P&gt;</description>
      <pubDate>Wed, 24 May 2023 11:00:39 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/is-legacy-single-user-standard-no-longer-supported/m-p/8047#M3775</guid>
      <dc:creator>grazie</dc:creator>
      <dc:date>2023-05-24T11:00:39Z</dc:date>
    </item>
    <item>
      <title>Re: Is LEGACY_SINGLE_USER_STANDARD no longer supported?</title>
      <link>https://community.databricks.com/t5/data-engineering/is-legacy-single-user-standard-no-longer-supported/m-p/8048#M3776</link>
      <description>&lt;P&gt;...and it works again - no changes made by us&lt;/P&gt;</description>
      <pubDate>Wed, 24 May 2023 12:16:34 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/is-legacy-single-user-standard-no-longer-supported/m-p/8048#M3776</guid>
      <dc:creator>grazie</dc:creator>
      <dc:date>2023-05-24T12:16:34Z</dc:date>
    </item>
    <item>
      <title>Re: Is LEGACY_SINGLE_USER_STANDARD no longer supported?</title>
      <link>https://community.databricks.com/t5/data-engineering/is-legacy-single-user-standard-no-longer-supported/m-p/76840#M35339</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;Can you please guide me where to edit this configuration, I could not edit the configuration in cluster compute. Please let me know how to add the above configuration in cluster compute.&lt;/P&gt;</description>
      <pubDate>Fri, 05 Jul 2024 06:19:24 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/is-legacy-single-user-standard-no-longer-supported/m-p/76840#M35339</guid>
      <dc:creator>saran2904</dc:creator>
      <dc:date>2024-07-05T06:19:24Z</dc:date>
    </item>
  </channel>
</rss>

