https://community.cloudera.com/t5/Support-Questions/Beeline-Configuration-hiveconf-Equivalent/m-p/163359#M125733 <P>Using a <STRONG>set</STRONG> works fine, correct. However, that requires that I do that for every script I try to automate. My goal is to make these values a default part of this base command, and just change what SQL I throw at it. Global values, if you will.</P><P>This should be remedied by the use of --hiveconf or --property-file, but neither results in it taking the values. Here's an example:</P><P><STRONG>Command:</STRONG></P><PRE>beeline -n $user -p $password -u "$jdbc_url" -f $script --verbose true --property-file "query.properties" --fastConnect </PRE><P><STRONG>query.properties</STRONG></P><PRE>hive.execution.engine=tez; tez.queue.name=di; hive.exec.parallel=true; </PRE><P>The job shows up in the 'default' queue when it should show up in the 'di' queue. When I use a set command, it does in fact show up in the 'di' queue.</P> Tue, 20 Dec 2016 05:14:58 GMT landon_t_robins 2016-12-20T05:14:58Z