<?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 Shared Hive External Metastore  Drop table issue in Data Governance</title>
    <link>https://community.databricks.com/t5/data-governance/shared-hive-external-metastore-drop-table-issue/m-p/20263#M712</link>
    <description>&lt;P&gt;hi Team ,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We are using a shared hive metastore for connecting to dev and prod as &lt;/P&gt;&lt;P&gt;we need cross DB access for certain ML use-cases.&lt;/P&gt;&lt;P&gt;Currently we are having issues as &lt;B&gt;"DROP TABLE COMMAND" &lt;/B&gt;directly drops the table without checking the underlying location&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Have anyone have a suggestion for avoiding this scenario or how to add storage based authorizatino in databrick&lt;/P&gt;&lt;P&gt;&lt;A href="https://cwiki.apache.org/confluence/display/Hive/Storage+Based+Authorization+in+the+Metastore+Server" target="test_blank"&gt;https://cwiki.apache.org/confluence/display/Hive/Storage+Based+Authorization+in+the+Metastore+Server&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;I&gt;Note: We cant have high concurrency cluster due to cost issues&lt;/I&gt;&lt;/P&gt;</description>
    <pubDate>Wed, 18 May 2022 08:30:05 GMT</pubDate>
    <dc:creator>Soma</dc:creator>
    <dc:date>2022-05-18T08:30:05Z</dc:date>
    <item>
      <title>Shared Hive External Metastore  Drop table issue</title>
      <link>https://community.databricks.com/t5/data-governance/shared-hive-external-metastore-drop-table-issue/m-p/20263#M712</link>
      <description>&lt;P&gt;hi Team ,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We are using a shared hive metastore for connecting to dev and prod as &lt;/P&gt;&lt;P&gt;we need cross DB access for certain ML use-cases.&lt;/P&gt;&lt;P&gt;Currently we are having issues as &lt;B&gt;"DROP TABLE COMMAND" &lt;/B&gt;directly drops the table without checking the underlying location&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Have anyone have a suggestion for avoiding this scenario or how to add storage based authorizatino in databrick&lt;/P&gt;&lt;P&gt;&lt;A href="https://cwiki.apache.org/confluence/display/Hive/Storage+Based+Authorization+in+the+Metastore+Server" target="test_blank"&gt;https://cwiki.apache.org/confluence/display/Hive/Storage+Based+Authorization+in+the+Metastore+Server&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;I&gt;Note: We cant have high concurrency cluster due to cost issues&lt;/I&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 18 May 2022 08:30:05 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-governance/shared-hive-external-metastore-drop-table-issue/m-p/20263#M712</guid>
      <dc:creator>Soma</dc:creator>
      <dc:date>2022-05-18T08:30:05Z</dc:date>
    </item>
  </channel>
</rss>

