<?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>question User should see only his/his group tables and HDFS directories(  level 1 or root directory) in Archives of Support Questions (Read Only)</title>
    <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/User-should-see-only-his-his-group-tables-and-HDFS/m-p/136533#M23382</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;We are running HDP2.3.4 cluster at Enterprise Level and
around 5 BI Business Units are connecting to the Hadoop cluster.&lt;/P&gt;&lt;P&gt;They are creating tables and importing files using Hive Views &amp;amp; HDFS Files View but here every BI Business unit is viewing
others tables( I mean only table names and not the data) in hive views and data
directories on HDFS as well(level 1 directory or root directory)&lt;/P&gt;&lt;P&gt;Based on Linux permission &amp;amp; Linux  group policies we implemented access control mechanism
on table’s data &amp;amp; sub directories but we are not able to hide table names
and parent directories(level 1 directory) in HDFS.&lt;/P&gt;&lt;P&gt;Suggest me if we have right solution?&lt;/P&gt;</description>
    <pubDate>Fri, 16 Sep 2022 10:10:24 GMT</pubDate>
    <dc:creator>divakarreddy_a</dc:creator>
    <dc:date>2022-09-16T10:10:24Z</dc:date>
    <item>
      <title>User should see only his/his group tables and HDFS directories(  level 1 or root directory)</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/User-should-see-only-his-his-group-tables-and-HDFS/m-p/136533#M23382</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;We are running HDP2.3.4 cluster at Enterprise Level and
around 5 BI Business Units are connecting to the Hadoop cluster.&lt;/P&gt;&lt;P&gt;They are creating tables and importing files using Hive Views &amp;amp; HDFS Files View but here every BI Business unit is viewing
others tables( I mean only table names and not the data) in hive views and data
directories on HDFS as well(level 1 directory or root directory)&lt;/P&gt;&lt;P&gt;Based on Linux permission &amp;amp; Linux  group policies we implemented access control mechanism
on table’s data &amp;amp; sub directories but we are not able to hide table names
and parent directories(level 1 directory) in HDFS.&lt;/P&gt;&lt;P&gt;Suggest me if we have right solution?&lt;/P&gt;</description>
      <pubDate>Fri, 16 Sep 2022 10:10:24 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/User-should-see-only-his-his-group-tables-and-HDFS/m-p/136533#M23382</guid>
      <dc:creator>divakarreddy_a</dc:creator>
      <dc:date>2022-09-16T10:10:24Z</dc:date>
    </item>
    <item>
      <title>Re: User should see only his/his group tables and HDFS directories(  level 1 or root directory)</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/User-should-see-only-his-his-group-tables-and-HDFS/m-p/136534#M23383</link>
      <description>&lt;P&gt;Database and table metadata is stored in the Hive Metastore, not in HDFS, so a different approach is needed to restrict this info from being sent to HiveServer2 clients.&lt;/P&gt;&lt;P&gt;This feature was added in Hive 1.2.0 by &lt;A href="https://issues.apache.org/jira/browse/HIVE-9350"&gt;HIVE-9350&lt;/A&gt;. You may need to use Ranger to achieve this functionality, which was added in &lt;A href="https://issues.apache.org/jira/browse/RANGER-238"&gt;RANGER-238&lt;/A&gt;. Both of these features are included in HDP 2.3.0+&lt;/P&gt;</description>
      <pubDate>Mon, 21 Mar 2016 21:26:56 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/User-should-see-only-his-his-group-tables-and-HDFS/m-p/136534#M23383</guid>
      <dc:creator>amiller</dc:creator>
      <dc:date>2016-03-21T21:26:56Z</dc:date>
    </item>
  </channel>
</rss>

