Re: queues, beeline/hs2 and tez

[Siddharth Seth <ss...@apache.org>]

+ user@hive.
This is specific to the way hive handles queues, and user@hive would be the
correct list to get an answer.

On Fri, Feb 26, 2016 at 3:21 PM, Stephen Sprague <sp...@gmail.com> wrote:

> hey guys (its me again!)
>
> this is a simple one i think.   i'm trying to set the tez.queue.name via
> the --hiveconf switch on beeline and it doesn't look to me it works.  the
> question is... should it?
>
>
> so this submits to the queue 'root.default' (which i don't want)
>
> {code}
> beeline \
>     --hiveconf tez.queue.name=dwr.low \
>     --hiveconf hive.execution.engine=tez \
>     -u "jdbc:hive2://dwrdevnn1.sv2.trulia.com:10001/default;auth=noSasl
> 'spragues' nopwd org.apache.hive.jdbc.HiveDriver"  \
>     --fastConnect=true  \
>     -e "select count(*), date_key from omniture.hit_data_aws group by
> date_key order by date_key"
> {code}
>
> while this submits to the queue 'dwr.low' (which i do want) but i don't
> want to add that clause in red. :(
>
> {code}
> beeline \
>     --hiveconf tez.queue.name=dwr.low \
>     --hiveconf hive.execution.engine=tez \
>     -u "jdbc:hive2://dwrdevnn1.sv2.trulia.com:10001/default;auth=noSasl
> 'spragues' nopwd org.apache.hive.jdbc.HiveDriver"  \
>     --fastConnect=true  \
>     -e "*set tez.queue.name <http://tez.queue.name>=dwr.low;* select
> count(*), date_key from omniture.hit_data_aws group by date_key order by
> date_key"
> {code}
>
> given i'm trying to write a general purpose sql wrapper i'd kinda like the
> first one to work b/c the sql string used in the -e switch is coming from
> the caller and i really don't want to inject my code into that if i can
> help it.
>
> anybody else run across this before? is there a trick?
>
> thanks,
> Stephen.
> PS  when hive.execution.engine=mr, --hiveconf mapred.job.queue.name=dwr.low
> works as advertised.
>

Re: queues, beeline/hs2 and tez

[Gopal Vijayaraghavan <go...@apache.org>]

> tez.queue.name via the --hiveconf switch on beeline and it doesn't look
>to me it works.  the question is... should it?

Nope, it shouldn't, because of Tez sessions the conf param is not job.

The tez.queue.name can be changed while a JDBC connection is up, so it is
not picked up from the conf & instead is acted upon when a user sends a
set command (i.e kill old session, start new session in the new queue).

>    -u "jdbc:hive2://dwrdevnn1.sv2.trulia.com:10001/default

This is what I do, might need adapting to the noSASL.

beeline   -u "jdbc:hive2://localhost:10000/default?tez.queue.name=adhoc"
-n gopalv --color=true   --outputformat=tsv2


Cheers,
Gopal