*Sent:* Friday, October 10, 2014 2:38 AM
>> *To:* user
>> *Subject:* mapreduce.job.queuename doesn't work with hiveserver2
>>
>>
>>
>> By setting mapreduce.job.queuename in hive-site.xml, all queries
>> submitted via hiveserver or hive cli all go to the specifi
2//url:1/db?mapreduce.job.queuename=q1
>
>
>
> *From:* Chen Song [mailto:chen.song...@gmail.com]
> *Sent:* Friday, October 10, 2014 2:38 AM
> *To:* user
> *Subject:* mapreduce.job.queuename doesn't work with hiveserver2
>
>
>
> By setting mapreduce.job.queue
You can change the mapreduce.job.queuename by appending it to connection string
after ‘?’ like jdbc:hive2//url:1/db?mapreduce.job.queuename=q1
From: Chen Song [mailto:chen.song...@gmail.com]
Sent: Friday, October 10, 2014 2:38 AM
To: user
Subject: mapreduce.job.queuename doesn't work
By setting mapreduce.job.queuename in hive-site.xml, all queries submitted
via hiveserver or hive cli all go to the specified queue.
However, hiveserver2 doesn't appear to respect this value at all. The queue
is chosen to be the user who submitted query. I tried with beeline and jdbc.
Is there a
