THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
JDBC connection URL: jdbc:hive2://<host>:<port>/<db>;ssl=true;twoWay=true;sslTrustStore=<trust_store_path>;trustStorePassword=<trust_store_password>;sslKeyStore=<key_store_path>;keyStorePassword=<key_store_password>?hive.server2.transport.mode=http;hive.server2.thrift.http.path=<http_endpoint>.
- <trust_store_path> is the path where client's truststore file lives. This is a mandatory non-empty field
- <trust_store_password> is the password to access the truststore.
- <key_store_path> is the path where client's keystore file lives. This is a mandatory non-empty field.
- <key_store_password> is the password to access the keystore.
Passing HTTP Header Key/Value Pairs via JDBC Driver
| Info | ||
|---|---|---|
| ||
This option is available starting in Hive 1.2.0. |
HIVE-10339 provided introduced an option for clients to provide custom HTTP headers that can be send sent to the underlying server (Hive 1.2.0 and later).
JDBC
...
connection
...
URL: jdbc:hive2://<host>:<port>/<db>?hive.server2.transport.mode=http;hive.server2.thrift.http.path=<http_endpoint>;http.header.<name1>=<value1>;http.header.<name2>=<value2>
When
...
the
...
above
...
URL
...
is
...
specified,
...
Beeline will
...
call
...
underlying
...
requests
...
to
...
add
...
an HTTP
...
header
...
set to
...
<name1>
...
and
...
<value1>
...
and
...
another
...
HTTP
...
header
...
set to
...
<name2>
...
and
...
<value2>. This
...
is
...
helpful
...
when
...
the
...
end
...
user
...
needs
...
to
...
send
...
identity
...
in
...
an HTTP
...
header
...
down
...
to
...
intermediate
...
servers
...
such
...
as
...
Knox
...
via
...
Beeline for
...
authentication, for example http.header.USERNAME=<value1>;http.header.PASSWORD=<value2>.