While the user may use any client program to connect to HiveServer2, the MR3 release provides a script for creating Beeline connections based on the configuration files in the installation.
In order to run Beeline, set the following environment variables in
env.sh as necessary:
USER_PRINCIPAL=gitlab-runner@RED USER_KEYTAB=/home/gitlab-runner/gitlab-runner.keytab HIVE_CLIENT_HEAPSIZE=2048
USER_KEYTABspecify the principal and keytab file for the user executing Beeline in a secure cluster with Kerberos.
HIVE_CLIENT_HEAPSIZEspecifies the heap size (in megabytes) for Beeline.
In order to start a Beeline connection, execute
hive/run-beeline.sh with the following options:
--local # Run jobs with configurations in conf/local/ (default). --cluster # Run jobs with configurations in conf/cluster/. --mysql # Run jobs with configurations in conf/mysql/. --tpcds # Run jobs with configurations in conf/tpcds/. --hivesrc1 # Choose hive1-mr3 (based on Hive 1.2.2) (default). --hivesrc2 # Choose hive2-mr3 (based on Hive 2.3.3). --hivesrc5 # Choose hive5-mr3 (based on Hive 3.1.0). --hiveconf <key>=<value> # Add a configuration key/value; may be repeated at the end. <Beeline option> # Add a Beeline option; may be repeated at the end.
The user can append as many Beeline options (for the command
beeline from Hive) as necessary to the command.
In a secure cluster with Kerberos, Beeline uses the Kerberos ticket provided by the user in order to authenticate itself to HiveServer2.
Hence the Kerberos ticket should be valid at the time of executing the script.
In a non-secure cluster without Kerberos, the script reads the environment variable
USER for both the user name and the password.
In order to override them, the user can supply Beeline options, as in
hive/run-beeline.sh -n username_foo -p password_bar.