Member since
12-14-2016
3
Posts
5
Kudos Received
0
Solutions
12-27-2016
10:56 AM
2 Kudos
One work around that I just tested - run the beeline with the following queue parameter: beeline -u "jdbc:hive2://local:10001/default;transportMode=http;httpPath=cliservice;principal=hive/_HOST@local.COM" -e "SELECT count(*) FROM log;" --hiveconf tez.queue.name=prd_am This will request the query to be executed in the prd_am queue. If the user has access to that queue allowed in Ranger, it will work fine. Still looking for a solution to use the default mapping defined in the YARN Capacity Scheduler configuration like: yarn.scheduler.capacity.queue-mappings=u:user1:dev_devs, g:devs:dev_devs
... View more