If you are using Knox, then it is just a pass through to connect to HiveServer2 via JDBC. So the policies should just work the same way as you will be connecting via beeline or any other JDBC client.
The best way to validate is to see how Ranger is allowing it. You can check Ranger Audit logs and it will tell you which policy allowed and for which user. Bosco On 8/15/17, 2:45 PM, "James Srinivasan" <[email protected]> wrote: Does Ranger support the same fine grained access control when Hive is accessed via JDBC versus when Hive is accessed via Knox/WebHCat? Our experience is that it works fine in the former case, but in the latter case the fine grained access control set in our Hive policies seems to be ignored. Many thanks
