<?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 Re: Hive UDFs restrictions in Ranger in Archives of Support Questions (Read Only)</title>
    <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Hive-UDFs-restrictions-in-Ranger/m-p/233488#M67300</link>
    <description>&lt;P&gt;Ok, thank you.&lt;/P&gt;</description>
    <pubDate>Mon, 04 Sep 2017 17:20:06 GMT</pubDate>
    <dc:creator>jiri_novak</dc:creator>
    <dc:date>2017-09-04T17:20:06Z</dc:date>
    <item>
      <title>Hive UDFs restrictions in Ranger</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Hive-UDFs-restrictions-in-Ranger/m-p/233484#M67296</link>
      <description>&lt;P&gt;Hi, &lt;/P&gt;&lt;P&gt;is it possible to restrict access to certain UDF (custom or built-in) in Ranger? &lt;/P&gt;&lt;P&gt;I have set the enableDenyAndExceptionsInPolicies option to true.
Then I created new access policy to deny a particular user access to all UDFs (* as database, * as udf, user in deny condition, all permissions selected). &lt;/P&gt;&lt;P&gt;This worked ok and the user was denied when tried to run a select with a function. &lt;/P&gt;&lt;P&gt;But when I put a particular function to the UDF field, the user was able to run the function. 
I tried it with a built-in function (unix_timestamp) as well as with a custom created function, and the result was the same. &lt;/P&gt;&lt;P&gt;What can be wrong or what else do I have to set up? &lt;/P&gt;&lt;P&gt;Thanks.&lt;/P&gt;</description>
      <pubDate>Fri, 25 Aug 2017 20:13:21 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Hive-UDFs-restrictions-in-Ranger/m-p/233484#M67296</guid>
      <dc:creator>jiri_novak</dc:creator>
      <dc:date>2017-08-25T20:13:21Z</dc:date>
    </item>
    <item>
      <title>Re: Hive UDFs restrictions in Ranger</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Hive-UDFs-restrictions-in-Ranger/m-p/233485#M67297</link>
      <description>&lt;P&gt;&lt;A href="https://community.hortonworks.com/users/43163/jirinovak.html"&gt;Jiri Novak&lt;/A&gt; which release is this ?&lt;/P&gt;&lt;P&gt;can you please check if you are hiting this issue RANGER-1631&lt;/P&gt;</description>
      <pubDate>Mon, 28 Aug 2017 14:01:28 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Hive-UDFs-restrictions-in-Ranger/m-p/233485#M67297</guid>
      <dc:creator>dsharma</dc:creator>
      <dc:date>2017-08-28T14:01:28Z</dc:date>
    </item>
    <item>
      <title>Re: Hive UDFs restrictions in Ranger</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Hive-UDFs-restrictions-in-Ranger/m-p/233486#M67298</link>
      <description>&lt;P&gt;Ranger is 0.7.0, Hive is 1.2.1000. &lt;/P&gt;&lt;P&gt;The RANGER-1631 issue is probably not related, as my problem is with evaluating the function name, not the database name, and it occurs when running the function, not when creating it. &lt;/P&gt;&lt;P&gt;I tried one more test: &lt;/P&gt;&lt;P&gt;I created an allow policy for select permission for the user with database=* and one particular UDF, and disabled all other policies for the user. &lt;/P&gt;&lt;P&gt;When this policy was disabled, the user could not run any UDFs. &lt;/P&gt;&lt;P&gt;When this policy was enabled, the user could run all UDFs, not just the one given in the policy.&lt;/P&gt;</description>
      <pubDate>Mon, 28 Aug 2017 19:13:28 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Hive-UDFs-restrictions-in-Ranger/m-p/233486#M67298</guid>
      <dc:creator>jiri_novak</dc:creator>
      <dc:date>2017-08-28T19:13:28Z</dc:date>
    </item>
    <item>
      <title>Re: Hive UDFs restrictions in Ranger</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Hive-UDFs-restrictions-in-Ranger/m-p/233487#M67299</link>
      <description>&lt;A rel="user" href="https://community.cloudera.com/users/43163/jirinovak.html" nodeid="43163"&gt;@Jiri Novak&lt;/A&gt;&lt;P&gt;Seems like the requirement is to enable Ranger policies at function level rather than the generic UDF level, this feature is not available for now.&lt;/P&gt;</description>
      <pubDate>Mon, 04 Sep 2017 13:23:21 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Hive-UDFs-restrictions-in-Ranger/m-p/233487#M67299</guid>
      <dc:creator>ssubhas</dc:creator>
      <dc:date>2017-09-04T13:23:21Z</dc:date>
    </item>
    <item>
      <title>Re: Hive UDFs restrictions in Ranger</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Hive-UDFs-restrictions-in-Ranger/m-p/233488#M67300</link>
      <description>&lt;P&gt;Ok, thank you.&lt;/P&gt;</description>
      <pubDate>Mon, 04 Sep 2017 17:20:06 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Hive-UDFs-restrictions-in-Ranger/m-p/233488#M67300</guid>
      <dc:creator>jiri_novak</dc:creator>
      <dc:date>2017-09-04T17:20:06Z</dc:date>
    </item>
  </channel>
</rss>

