THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
HiveServer2 provides support for sending Thrift RPC messages over HTTP transport (Hive 0.13 onward, see HIVE-4752). This is particularly useful to support a proxying intermediary between the client and the server (for example, for load balancing or security reasons). Currently, you can run HiveServer2 in either TCP mode or the HTTP mode, but not in both. For the corresponding JDBC URL , check this link: HiveServer2 Clients -- JDBC Connection URLs. Use the following settings to enable and configure HTTP mode:
| Setting | Default |
|---|
...
| Description |
|---|
| hive.server2.transport.mode |
...
| binary | Set |
...
| to http |
...
Cookie Based Authentication
...
Optional Environment Settings
...
| to enable HTTP transport mode |
| hive.server2.thrift.http. |
...
| port | 10001 |
| HTTP port number to listen on |
...
| hive.server2.thrift.http |
...
| .max.worker.threads | 500 | Maximum worker threads in the server pool |
| hive.server2.thrift.http.min.worker.threads |
...
| 5 | Minimum worker threads in the server pool | |
| hive.server2.thrift.http.path | cliservice | The service endpoint |
| Panel |
|---|
Cookie Based AuthenticationHIVE-9709 and HIVE-9710 introduced cookie based authentication for HiveServer2 in HTTP mode. The HiveServer2 parameters (; default is 5.hive.server2.thrift.http.max.worker.threads – Maximum worker threads in the server pool; default is 500cookie.*) associated with this change can be found here. |
Optional Global Init File
...